subject:"\[racket\] Debugging a seg fault"

Re: [racket] Debugging a seg fault

2013-10-24 Thread Tobias Hammer

My normal workflow for this (preferring post-mortem analysis because no special flags for gdb required) enable core dumps ulimit -c unlimited cat segv.rkt #lang racket (require ffi/unsafe) (define _strlen (get-ffi-obj "strlen" #f (_fun _pointer -> _int))) (_strlen #f) racket segv.rkt SI

[racket] Debugging a seg fault

2013-10-24 Thread Chad Albers

I working on a small test program using Jay McCarthy's zmq FFI bindings. I'm getting a segfault with this message: SIGSEGV MAPERR si_code 1 fault on addr 0x285 Is there any guidance on how to spot the cause? Here's what I have done so far run racket with gdb - as gdb racket In the gdb console.