0007135: Too many debuggers pop up repeatedly on errors.

Viewing Issue Simple Details [ Jump to Notes ]

[ View Advanced ] [ Issue History ] [ Print ]

Category

Severity

Reproducibility

Date Submitted

Last Update

0007135

[Squeak] Morphic

major

always

07-28-08 00:07

07-28-08 18:11

Reporter

wiz

View Status

public

Assigned To

Priority

low

Resolution

open

Status

new

Product Version

Summary

0007135: Too many debuggers pop up repeatedly on errors.

Description

In 3.10.2 and other images errors seem to popup continuously after the first one.

I don't have a solid example right now.
But the general annoyance from this problem prompts a complaint.

Additional Information

Analysis.

There are 31-2 callers of #displayWorld
displayWorld is the inner call of #displayWorldSafelyFor:

#displayWorldSafelyFor: sets up an error handling context for
#displayWorld.
So apparently bypassing it has started to cause problems.

1st Q: Should the other callers use #displayWorldSafely instead?

Attached Files

Relationships

Notes
(0012418 - 583 - 631 - 631 - 631 - 631 - 631) wiz 07-28-08 18:11	Hmm. Back to the drawing board. I made a test ErrorProneMorph. When it's checkbox is activated it causes an error to be thrown during drawing. Playing with it did not raise recursive debugger but caused me to rethink my reasoning. As long as displayWorldSafely is periodically called morphs with drawing errors will be caught and flagged. So it will not matter if at other times displayWorldSafely is bypassed. It would have to ALWAYS be bypassed in order for the mechanism to fail and recursive debugging to begin. So the recursive debuggers are due to something else.

Issue History
Date Modified	Username	Field	Change
07-28-08 00:07	wiz	New Issue
07-28-08 18:11	wiz	Note Added: 0012418

Mantis 1.0.8[^]

31 total queries executed.
26 unique queries executed.