On Fri, Aug 08, 2014 at 09:11:30AM +0200, Arie Peterson wrote: > On Thursday 07 August 2014 23:08:01 Arnt Gulbrandsen wrote: > > > By 'archiveopteryx', you mean the binary 'aox', I suppose? > > > > No. sbin/archiveopteryx. > > Right. I get a very similar crash for that one:
The gdb command to catch it is "handle sigill stop nopass". Please run it and when it crashes (and gdb catches the signal), use the "bt" command, which will give you a stack trace. I'm afraid I can't test this on my raspberry pi; the box hasn't enough storage and I won't be able to upgrade for many months. > > This doesn't sound like an aox bug. > > > > Make sure to build with -g. > > I did not change anything about the build (just 'jam && jam install'). Where > can I check whether this option was enabled, and what does it do? That's how you tell the compiler and linker to include debugging information in the executable. When you build, you see many lines like "clang ... -g" or "g++ ... -g", and then gdb will be able to tell you useful things about which functions called each other. Arnt
