Re: Re: New step-until-code-is-available feature request (was: call for input, votes)

Wouldn't using the 'exclude' command to exclude "javax.*" solve this
problem? While I do not object to the auto-exclude feature, it just
seems like there is already a perfectly good solution.

n


On Wed, 2002-06-12 at 14:20, Paul Legato wrote:
> How about a new step instruction that will tell JSwat to continue 
> executing normally until execution reaches a class for which source is 
> available?
> 
> Frequently when I'm debugging a Swing application, I'll set a breakpoint 
> and start stepping through my code, but then the instruction pointer 
> will pass outside of my code into a long list of Swing classes, about 
> which JSwat complains that it has no source available every time I tell 
> it to step. Even stepping over methods doesn't help much, since the next 
> method up is typically a Swing method also. It'd be nice to tell it to 
> just run normally until it hits a class for which a .java file is 
> available, and then break and revert to single stepping.
> 
> Kind of like an automatic "exclude"...
> 
> -Paul