<div dir="ltr">How about doing this:<div><br></div><div>gdb racket -l drracket</div><div><br></div><div>from the command line and then, when gdb shows up, type "run" and hit return. Then you should get a stack trace, at least.</div> <div><br></div><div>Robby</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Sat, Apr 27, 2013 at 4:39 PM, Patrick King <span dir="ltr"><<a href="mailto:slowthought@gmail.com" target="_blank">slowthought@gmail.com</a>></span> wrote:<br> <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div class="im">On Sat, Apr 27, 2013 at 5:02 PM, Robby Findler <span dir="ltr"><<a href="mailto:robby@eecs.northwestern.edu" target="_blank">robby@eecs.northwestern.edu</a>></span> wrote:<br> <blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div>I'm not sure how to better communicate with ubuntu, but if you run drracket from a shell / terminal window then there might be some output in that window after the crash happens that might be a hint.</div> <br></blockquote><div> </div></div><div>pking@pk-Aspire-5733Z:~/Source$ ./drracket.sh<br> Seg fault (internal error) at 0x7f20eb35aa40<br> SIGSEGV SEGV_ACCERR SI_CODE 2 fault on 0x7f20eb35aa40<br> ./drracket.sh: line 2: 2470 Aborted (core dumped) /usr/racket/bin/drracket<br> pking@pk-Aspire-5733Z:~/Source$ <br><br></div><div>I haven't found where the core dump is actually hiding. There is no line 2470 in usr/racket/bin/drracket, which is what ./drracket.sh: line 2 appears to reference. It might refer to a line deep in the gracket source.<br> <br></div><div>Thanks, Pat.<br></div><div> </div></div><br></div></div> </blockquote></div><br></div>