Segmentation fault when typing ls in taskbrowser after execution of a command

Segmentation fault when typing ls in taskbrowser after execution

[This is a resend as the mailinglist manager complained about the message
size]
On Friday 30 May 2008 16:13:53 Tinne De Laet wrote:
> Hi,
>
> I get this strange segmentation fault and I'm quite out of ideas to fix it.
> I use the deployer.
> Next I start my component.
> After this ls just works fine.
> Then I execute a command (InitLoops()).
> After this execution ls results in a segmentation fault.
> The report file I get from the reporter however contains usefull and
> meaningfull results.
> Any idea what I can do.
>
> I also tried y.Get() and so long but this all results in a segmentation
> fault.

Just to rule things out... you should really avoid to import 'wrong'
libraries. Just doing an import of /usr/local/orocos/lib is asking for
trouble. I know that the ocl components should be in a subdirectory of lib,
preferably per OS. But until then, don't just import everything.

Second, compiling the RTT with debug info really helps us out in
these 'corner' cases, as a backtrace gives line number and argument contents
information.

The function that crashes is names(). The only way this could happen is that
the AttributeRepository has been corrupted. It's not destroyed because
properties are stored inthere as well.

Anyway, first get rid of the massive import statements.

Peter

Segmentation fault when typing ls in taskbrowser after execution

On Friday 30 May 2008 16:13:53 Tinne De Laet wrote:
> Hi,
>
> I get this strange segmentation fault and I'm quite out of ideas to fix it.
> I use the deployer.
> Next I start my component.
> After this ls just works fine.
> Then I execute a command (InitLoops()).
> After this execution ls results in a segmentation fault.
> The report file I get from the reporter however contains usefull and
> meaningfull results.
> Any idea what I can do.
>
> I also tried y.Get() and so long but this all results in a segmentation
> fault.

If this iTasc component is really big, try to compile it for gnulinux and test
it with valgrind. It may be that your code has a bug (triggered by the
command), overwriting the wrong memory and causing the segfault later on..

Peter