Re: Breakpoints in "unrolled loop"
- From: Oliver Betz <OBetz@xxxxxxxxxxxxx>
- Date: Sun, 30 Sep 2007 16:47:30 +0200
Hans-Bernhard Bröker wrote:
what's the behaviour of your debugger(s) when the code contains
unrolled loops, IOW one source statement corresponds to many locations
in the binary?
I don't see why that should pose any particular problem. Debug
information is usually stored as a function of binary location, i.e. you
give it a binary location, and it looks up the source location from that.
if you select a source statement to set a breakpoint, the debugger has
to select which binary location(s) get a breakpoint.
In single step, I would set the breakpoint at the next corresponding
binary location. When setting a breakpoint during program execution
(e.g. by background debug mode), I would set a breakpoint at _each_
corresponding location, since I can't know the PC at the time of
breakpoint setting.
This can be impossible with massively unrolled loops and/or limited
hardware breakpoints.
It's usually the *opposite* case that causes troubles, i.e. when code
folding has turned multiple copies of the same functionality into a
ack, that's indeed hard.
Oliver
--
Oliver Betz, Muenchen (oliverbetz.de)
.
- Follow-Ups:
- Re: Breakpoints in "unrolled loop"
- From: Hans-Bernhard Bröker
- Re: Breakpoints in "unrolled loop"
- References:
- Breakpoints in "unrolled loop"
- From: Oliver Betz
- Re: Breakpoints in "unrolled loop"
- From: Hans-Bernhard Bröker
- Breakpoints in "unrolled loop"
- Prev by Date: Re: 78K0 programming
- Next by Date: Re: Breakpoints in "unrolled loop"
- Previous by thread: Re: Breakpoints in "unrolled loop"
- Next by thread: Re: Breakpoints in "unrolled loop"
- Index(es):
Relevant Pages
|
