From: Glenn T. <gt...@um...> - 2008-04-19 22:08:13
|
Hi, I hope this isn't an inappropriate question. I'm climbing the lisp learning curve with SBCL. I've been trying to get line numbers to show up in stack traces, but have been unsuccessful so far. I've set my compile declarations to: (declaim (optimize (speed 0) (safety 3) (debug 3) (space 0))) But that doesn't seem to help any. Is there some other setting (I was unable to find anything in the manual)? Thanks, Glenn |
From: Zach B. <xa...@xa...> - 2008-04-19 22:12:29
|
On Sat, Apr 19, 2008 at 06:07:05PM -0400, Glenn Tarcea wrote: > Hi, > > I hope this isn't an inappropriate question. I'm climbing the lisp > learning curve with SBCL. I've been trying to get line numbers to > show up in stack traces, but have been unsuccessful so far. I've set > my compile declarations to: > > (declaim (optimize (speed 0) (safety 3) (debug 3) (space 0))) > > But that doesn't seem to help any. Is there some other setting (I was > unable to find anything in the manual)? http://jsnell.iki.fi/blog/archive/2007-12-19-pretty-sbcl-backtraces.html has an example of how to do it. Do you use SLIME? With slime, at the appropriate debug levels, using "v" in a frame will jump straight to the form that caused the error. Zach |
From: Glenn T. <gt...@um...> - 2008-04-20 14:12:23
|
Thanks. I'll give it's method a try. Right now I'm using CUSP which is an Eclipse plugin for Lisp. It doesn't quite have all the functionality of emacs with Slime, but is a little more user friendly. Unfortunately it doesn't support the method below. I may switch to Emacs/Slime at some point. I went with CUSP because Eclipse is an environment I'm familiar with and I wanted to get up and running quickly. Thanks for the reply! Glenn On Apr 19, 2008, at 6:12 PM, Zach Beane wrote: > On Sat, Apr 19, 2008 at 06:07:05PM -0400, Glenn Tarcea wrote: >> Hi, >> >> I hope this isn't an inappropriate question. I'm climbing the lisp >> learning curve with SBCL. I've been trying to get line numbers to >> show up in stack traces, but have been unsuccessful so far. I've set >> my compile declarations to: >> >> (declaim (optimize (speed 0) (safety 3) (debug 3) (space 0))) >> >> But that doesn't seem to help any. Is there some other setting (I was >> unable to find anything in the manual)? > > http://jsnell.iki.fi/blog/archive/2007-12-19-pretty-sbcl- > backtraces.html > has an example of how to do it. > > Do you use SLIME? With slime, at the appropriate debug levels, using > "v" in a frame will jump straight to the form that caused the > error. > > Zach > > ---------------------------------------------------------------------- > --- > This SF.net email is sponsored by the 2008 JavaOne(SM) Conference > Don't miss this year's exciting event. There's still time to save > $100. > Use priority code J8TL2D2. > http://ad.doubleclick.net/clk;198757673;13503038;p?http:// > java.sun.com/javaone > _______________________________________________ > Sbcl-devel mailing list > Sbc...@li... > https://lists.sourceforge.net/lists/listinfo/sbcl-devel > > |