As a first step, try gdb like this: $ gdb racket (gdb) handle SIGSEGV nostop noprint (gdb) run ... [arguments to run your program] ... (gdb) where
to get a backtrace. Depending on the output, we should have an idea for the next step. At Thu, 27 Oct 2016 20:55:52 +0100, Erich Rast wrote: > Hi! > > I have a bug that in the Linux version of a mid-sized program (closed > source) that causes the program to immediately crash and also causes > DrRacket to immediately crash once the command key is pressed in some > editor in a tab panel of an open frame. No console output, hard crashes > to desktop. The bug exists for a while already, since at least Racket > 6.5, I just didn't have the time to take a look at it yet. > > I cannot give away the source code but was wondering whether there is a > way to debug this, some external debugger or commandline flag for > racket that might give me some clue, any clue whatsoever, about what's > going on. > > Any advice? > > Best, > > Erich > > -- > You received this message because you are subscribed to the Google Groups > "Racket Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to racket-users+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "Racket Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to racket-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
