On 01/24/2013 07:26 PM, Stephen Paul Weber wrote: > Somebody claiming to be Nathan Hüsken wrote: >> On 01/24/2013 07:00 PM, Stephen Paul Weber wrote: >>> Somebody claiming to be Karel Gardas wrote: >>>> On 01/24/13 05:51 PM, Stephen Paul Weber wrote: >>> So, not sure on the right solution, but when I add -lcaps then the >>> linker errors go away and I can build executables. Unfortunately, when >>> I try to run any of them on a device, I get a segfault, just as I always >>> did with registerised cross-builds for ARM... this with both llvm-3.0 >>> and llvm-3.2 >>> >>> :( >>> >> Can you run it in gdb and loock what the backtrace looks like? > > [New pid 14037182 tid 1] > Program terminated with signal 11, Segmentation fault. > #0 0x08502000 in ?? () > (gdb) bt > #0 0x08502000 in ?? () > #1 0x082ce4c4 in ?? () > #2 0x082ce4c4 in ?? () > Backtrace stopped: previous frame identical to this frame (corrupt stack?) > (gdb)
Not very informative :). Did you compile with -debug? I remember I got a stack trace with gdb like this (when doing remote debugging) and got it cleaned up by loading the exectuable with "file". Maybe you have to do something like that to? _______________________________________________ Glasgow-haskell-users mailing list Glasgow-haskell-users@haskell.org http://www.haskell.org/mailman/listinfo/glasgow-haskell-users
