On Thursday 28 December 2000 15:32, Karl Goiser wrote:
My question is: is there a way to log message sends to a file so I can see what is executing? Otherwise, when in the debugger, is it possible to look at the source of the methods being executed?
Well, there's printCallStack() that you could call from C (you don't say what platform you're running, but using the WinCE remote debugger, I can break program execution, then evaluate printCallStack(); this will print out the call stack on the console (stderr or stdout for regular Win32 or Unix, I imagine).
Thanks for the Ned. I'm on the mac in Codewarrior, so I don't think I can call a function from within the debugger. Somebody else suggested I write it into the event code conditional upon a global which I could then turn on whenever I wanted to...
Best wishes,
Karl
on 29/12/00 10:50 AM, Ned Konz at ned@bike-nomad.com wrote:
On Thursday 28 December 2000 15:32, Karl Goiser wrote:
My question is: is there a way to log message sends to a file so I can see what is executing? Otherwise, when in the debugger, is it possible to look at the source of the methods being executed?
Well, there's printCallStack() that you could call from C (you don't say what platform you're running, but using the WinCE remote debugger, I can break program execution, then evaluate printCallStack(); this will print out the call stack on the console (stderr or stdout for regular Win32 or Unix, I imagine).
Karl Goiser wrote:
Thanks for the Ned. I'm on the mac in Codewarrior, so I don't think I can call a function from within the debugger. Somebody else suggested I write it into the event code conditional upon a global which I could then turn on whenever I wanted to...
consider running the IntepreterSimulator; then you can debug in Smalltalk! It can be too slow on some machines or under some circumstances, but you'd be amazed how powerful it can be.
tim
squeak-dev@lists.squeakfoundation.org