Re: Breakpoints in "unrolled loop"
- From: Hans-Bernhard Bröker <HBBroeker@xxxxxxxxxxx>
- Date: Sun, 30 Sep 2007 20:51:09 +0200
Oliver Betz wrote:
Hans-Bernhard Bröker wrote:
if you select a source statement to set a breakpoint, the debugger hasNot quite true. Somebody has to make that decision, but it doesn't have to be done by the tool alone. I've seen at least one debugger offer a complete selection of eligible code addresses in such cases.
to select which binary location(s) get a breakpoint.
This would be fine. Do you remember which debugger did so?
ACCEMIC MDE, a debugger for Fujitsu 16-bit and 32-bit controllers.
Personally I think I'd prefer a tool that sets a breakpoint on the first copy in this case (assuming that it's really just an unrolled loop) or generally on the entry point into the unrolled portion.
If there are function calls with long (potential) duration in the
loop, this could delay the breakpoint hit.
But only for as long as the whole unrolled loop takes to return to its beginning. Unless that loop covers the majority of program execution time, odds are the code will be *outside* the loop the moment the breakpoint is set.
.
- References:
- Breakpoints in "unrolled loop"
- From: Oliver Betz
- Re: Breakpoints in "unrolled loop"
- From: Hans-Bernhard Bröker
- Re: Breakpoints in "unrolled loop"
- From: Oliver Betz
- Re: Breakpoints in "unrolled loop"
- From: Hans-Bernhard Bröker
- Re: Breakpoints in "unrolled loop"
- From: Oliver Betz
- Breakpoints in "unrolled loop"
- Prev by Date: Re: Breakpoints in "unrolled loop"
- Next by Date: Re: which micro to pick
- Previous by thread: Re: Breakpoints in "unrolled loop"
- Next by thread: jtagice mk1
- Index(es):
Relevant Pages
|