Re: New step-until-code-is-available feature request (was: call for input, votes)
Paul Legato <[email protected]>
| Newsgroups | gmane.comp.java.jswat.user |
|---|---|
| Message-ID | <[email protected]> |
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 Nathan Fiedler wrote: > Given the number of bugs and feature requests in the JSwat bugs > database, I would like to hear what you think needs to be addressed. > > For a list of the open issues, look at > http://www.bluemarsh.com/bugzilla/ and query for all "JSwat" product > bugs. This shows bugs as well as feature requests. As a registered user > you get a total of 10 votes (one vote per bug). So far there are only > two bugs with any votes, each with only one vote. > > In addition to the open issues, if you can think of any problems you > have encountered when using JSwat, I would like to hear about them. For > instance, error messages that didn't make sense, or features that are > confusing or misleading. And by no means is this request restricted to > bugs. If you have a feature request, please send it to me. > > thanks > > nathan > > > _______________________________________________ > jswat-user mailing list > [email protected] > http://www.bluemarsh.com/mailman/listinfo/jswat-user