[Pharo-dev] Debugging a failing test doesn't include the full stack

Esteban A. Maringolo emaringolo at gmail.com
Wed Nov 25 15:32:11 EST 2015

2015-11-25 6:32 GMT-03:00 Guillermo Polito <guillermopolito at gmail.com>:
> I’ve seen this problem tons of times since Pharo4. But the worst is that I
> never found a way to reproduce it.
> To me there is some side effect somewhere. Because it does not happen in a
> fresh image, but once you have it, you have it all the time.

I thought it had to do with how GLORP handles the exceptions and/or
block unwinding. But it doesn't seem so.

There is a bug report for this:

Esteban A. Maringolo

More information about the Pharo-dev mailing list