Thread: [ANNOUNCE] Columbus Navigation Toolkit
View Single Post
avidscavenger is offline avidscavenger
2013-04-20 , 01:26
Posts: 96 | Thanked: 80 times | Joined on May 2010
#287
Ah OK I see I was missing the community-testing repo.

I don't think I need any more core dumps, since they all look pretty much the same:

Program terminated with signal 11, Segmentation fault.
#0 0x40e7d098 in QString::fromLatin1_helper(char const*, int) () from /usr/lib/libQtCore.so.4
0x40e7d098 <_ZN7QString17fromLatin1_helperEPKci+76>: ldrb r3, [r8]
(gdb) bt
#0 0x40e7d098 in QString::fromLatin1_helper(char const*, int) () from /usr/lib/libQtCore.so.4
#1 0x40e8710c in QString::fromAscii_helper(char const*, int) () from /usr/lib/libQtCore.so.4
#2 0x00015c24 in ?? ()
#3 0x00015c24 in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
I don't really know enough about arm architecture to say with any certainty whether this really is likely to be a corrupt stack, a bug in gdb or something else.

What I do notice however is that if columbus is compiled with optimisation level 2 or higher then it crashes while with level 1 or lower it seems to be OK. Possibly the code does something weird that doesn't work when the compiler tries to optimise it?

But this does suggest an ugly work-around... just build it with a lower level of compiler optimisation.
 

The Following 2 Users Say Thank You to avidscavenger For This Useful Post: