|
 FAQ-O-Matic : General : Debugger :
I've set a breakpoint in a file. The debugger stops at the breakpoint. When I click the icon to single-step to the next line, the debugger takes off at a run, just like I'd pressed the 'run' icon instead. What gives? |
| Hin Boen writes:
This can happen if you add a line breakpoint in the class that has been marked as tracing disabled (see Run | View Classes With Tracing Disabled ... ). If this is the case, JBuilder will still hit your breakpoint, but when you single-step, JBuilder will keep on stepping until it hits another breakpoint or stops at a class with tracing disabled off. To verify if that is the case, when you hit the line-breakpoint, turn the SmartStep off, and proceed with the single-step. Editor's note: This is unlikely to be the cause of the problem if you're using JBuilder Foundation because the 'Smart Step' debugger feature is disabled in Foundation. So, if JB4F takes off after a breakpoint, there is something else wrong.
| |
| There is also a theory that suggests SmartStep loses control when asked to step-over an ignored class method which contains a wait() call.
You may need to disable Smart Step and set some additional breakpoints before/after the call in question to regain control of the debugger. | |
| [Append to This Answer] | |
| 2001-May-03 6:56pm |
| ||||||||
|
Java Community
Java Tools |
Code Central JB OpenTools |
Community Recent Threads |
Borland Chat Chat FAQ |
||||||||||||||
|
Feature Matrices 3.0 | 3.5 | 4.0 5.0 | 6.0 | 7.0 |
Shop for JBuilder |
JBuilder Downloads and reg keys |
Report Piracy | ||||||||||||||
|
Online Manuals 4.0 | 5.0 | 6.0 7.0 |
Borland DevSupport's Bug/RFE Form Quality Central Client |
JB Patches & Updates |
JBuilder FAQs TIs | ||||||||||||||
|
JBuilder Newsgroups |
Tamaracka's News Archive |
Mr. Haki's JBuilder Machine |
JGuru's JBuilder FAQ |
||||||||||||||
|
Sun's Bug Parade |
|||||||||||||||||
|
|||||||||||||||||
I have JBuilder4 Enterprise. Where is the advertised debugger feature "Synchronization Monitors??" used for diagnosing deadlock conditions?
