I had a prototype working at a certain point that send the exception to the debugger.

I'll see if I can dig it up. It just involved chancing the API methods that open the debugger. Maybe a bit late for Pharo 6.

On Sun, Nov 6, 2016 at 11:04 PM, Bernardo Ezequiel Contreras <vonbecmann@gmail.com> wrote:

+1, with that information you could describe or show the cause of the exception

On Sun, Nov 6, 2016 at 6:46 AM, Sven Van Caekenberghe <sven@stfx.eu> wrote:
Indeed this has bothered me a lot as well.

At least an 'Inspect Exception' would be useful.

It would also encourage people to put more useful information inside exception objects.

> On 6 Nov 2016, at 10:38, Yuriy Tymchuk <yuriy.tymchuk@me.com> wrote:
>
> Hi,
>
> we have this supercool exception handling mechanism, but as soon as we open a debugger the exception object is gone�� I understand that we didn��t need this in old times, but now with a moldable debugger, we could create hooks to allow exceptions to define how they should be addressed (and objects are really powerful).
>
> Cheers.
> Uko

--
Bernardo E.C.

Sent from a cheap desktop computer in South America.