Anyway, if you pull the halo on the debugger, you should be able to click
the wrench, which will give you an inspector that you can use to drill down into the actual stack trace.
Too bad the drill down process wasn't explained. Now what does one do to get the stack copied?
At the right of the top pane of the Debugger above the scrollers is a little square that brings up a Context menu which has at the bottom 'mail out bug report'. Click it (it doesn't mail it out right away), then enter a fake email address, I use a@b.c, which then opens up a Mister Postman window with the stack info you are looking for. Copy and paste that where you want. I suppose you can use a real email address, I've never tried actually mailing the message out from Squeak.
Ken
At 10:47 AM -0700 9/13/11, Overcomer Man apparently wrote:
Anyway, if you pull the halo on the debugger, you should be able to click the wrench, which will give you an inspector that you can use to drill down into the actual stack trace.
Too bad the drill down process wasn't explained. Now what does one do to get the stack copied?
Beginners mailing list Beginners@lists.squeakfoundation.org http://lists.squeakfoundation.org/mailman/listinfo/beginners
On 13.09.2011, at 10:47, Overcomer Man wrote:
Anyway, if you pull the halo on the debugger, you should be able to click the wrench, which will give you an inspector that you can use to drill down into the actual stack trace.
Too bad the drill down process wasn't explained. Now what does one do to get the stack copied?
The stack is automatically logged to a file named SqueakDebug.log in the default directory. Just attach that. Watch out though, it gets overwritten on the next error.
- Bert -
beginners@lists.squeakfoundation.org
-
Bert Freudenberg -
Ken G. Brown -
Overcomer Man