At Sat, 25 Aug 2012 20:04:45 +0100 (BST), Jan Wedekind wrote: > I tried to debug > However then the > program reports the following segmentation fault instead: > > Program received signal SIGSEGV, Segmentation fault. > 0x00282540 in scheme_gmp_tls_unload (s=0x4031cedc, data=0x0) at > ./gmp/gmp.c:5813 > 5813 s[0] = 0; > (gdb) l > 5808 void scheme_gmp_tls_unload(intptr_t *s, void *data) > [...] > > According to [2] this is a GC write barrier and one needs to ignore > semgentation faults as follows > > (gdb) handle SIGSEGV nostop noprint
Yes. > But in that case it is not possible to debug the initial segmentation fault > though. Does it work to set a breakpoint on abort()? (gdb) br abort _________________________ Racket Developers list: http://lists.racket-lang.org/dev
