<div dir="ltr">Oh, but maybe this is the right way to do things:<div><br></div><div><div>[robby@yanpu] ~/git/plt/src/build$ gdb `which racket`</div><div>GNU gdb 6.3.50-20050815 (Apple version gdb-1705) (Fri Jul 1 10:50:06 UTC 2011)</div>
<div>Copyright 2004 Free Software Foundation, Inc.</div><div>GDB is free software, covered by the GNU General Public License, and you are</div><div>welcome to change it and/or distribute copies of it under certain conditions.</div>
<div>Type "show copying" to see the conditions.</div><div>There is absolutely no warranty for GDB. Type "show warranty" for details.</div><div>This GDB was configured as "x86_64-apple-darwin"...Reading symbols for shared libraries ... done</div>
<div><br></div><div>(gdb) set args -l drracket</div><div>(gdb) run</div><div>Starting program: /Users/robby/git/exp/plt/bin/racket -l drracket</div></div><div><br></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">
On Sat, Apr 27, 2013 at 5:15 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:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">I'm not following. I meant "- ell", fwiw. Here's what I see on my mac os x machine:<div><br></div><div><div>[robby@yanpu] ~/git/plt/src/build$ gdb racket -l drracket</div><div>warning: could not set timeout limit to `drracket'.</div>
<div>GNU gdb 6.3.50-20050815 (Apple version gdb-1705) (Fri Jul 1 10:50:06 UTC 2011)</div><div>Copyright 2004 Free Software Foundation, Inc.</div><div>GDB is free software, covered by the GNU General Public License, and you are</div>
<div>welcome to change it and/or distribute copies of it under certain conditions.</div><div>Type "show copying" to see the conditions.</div><div>There is absolutely no warranty for GDB. Type "show warranty" for details.</div>
<div>This GDB was configured as "x86_64-apple-darwin"...Reading symbols for shared libraries ... done</div><div><br></div><div>(gdb) run</div><div>Starting program: /Users/robby/git/exp/plt/bin/racket </div><div>
<br></div><div><br></div></div></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><br><div class="gmail_quote">On Sat, Apr 27, 2013 at 5:09 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><div><div><div>gdb racket -"ell"<br></div>gdb racket -"one"<br></div>gdb racket -"eye"<br>
<br></div>Good to have gdb back, down in the guts. appalling how much I've forgotten. Most likely error message so far:<br>
<br>~/Source$ gdb racket -i drracket<br> Interpreter `drracket' unrecognized<br>~/Source$<br><br></div>I've tried running from home, usr directories, various variations of ./* for file references.<br></div><div>
<div><div class="gmail_extra">
<br><br><div class="gmail_quote">On Sat, Apr 27, 2013 at 5:42 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:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<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>
<span><font color="#888888">
<div><br></div><div>Robby</div></font></span></div><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>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>
</div></div></blockquote></div><br></div>
</div></div></blockquote></div><br></div>
</div></div></blockquote></div><br></div>