On Wednesday 12 February 2003 10:16 pm, Adam Spitz wrote:
> Hopefully I'm wrong. Is there a reliable way for a
> Debugger object to get access to the Exception object
> that caused it to be created?

The Debugger has a contextStackTop instvar: that will be the 
doesNotUnderstand: context; the first argument of that top context 
will be the Message that isn't understood.

So (from the Debugger) you should be able to get the Message by

self interruptedContext tempAt: 1

Here's what I did to find that, BTW:

send a bogus message to an object.
PreDebugWindow is created.
Bring up halo on PreDebugWindow, and explore the Morph.
expand model (which is a Debugger).
notice contextStackTop; look at it.
voila!

-- 
Ned Konz
http://bike-nomad.com
GPG key ID: BEEA7EFE