On Fri, May 10, 2013 at 9:19 PM, Jon Zeppieri <zeppi...@gmail.com> wrote: [snip]
> > Any idea where to look or what debugging tools might be useful? Sorry, I should have mentioned that the segfault does appear to occur in jitted code. And it occurs trying to treat the character as a pointer and dereference it. Here's an example of it trying to dereference #\c: Program received signal EXC_BAD_ACCESS, Could not access memory. Reason: KERN_INVALID_ADDRESS at address: 0x0000000000006302 0x00000001081dc110 in ?? () (gdb) bt #0 0x00000001081dc110 in ?? () #1 0x0000000105d9727b in ?? () #2 0x0000000107f6721d in ?? () #3 0x00000001049684b2 in scheme_do_eval (obj=0x0, rands=0x7fff5b2fb218, num_rands=94641560, get_value=1529852240) at schthread.h:381 #4 0x000000010499c62e in for_each (argv=0x105a41f18, argc=8) at schmap.inc:106 #5 0x0000000105d977eb in ?? () #6 0x0000000107f66d18 in ?? () ... _________________________ Racket Developers list: http://lists.racket-lang.org/dev
