This is the mail archive of the
gdb-patches@sources.redhat.com
mailing list for the GDB project.
Re: [PATCH RFA] TARGET_ADJUST_BREAKPOINT_ADDRESS...
- To: Andrew Cagney <ac131313 at cygnus dot com>
- Subject: Re: [PATCH RFA] TARGET_ADJUST_BREAKPOINT_ADDRESS...
- From: Kevin Buettner <kevinb at cygnus dot com>
- Date: Mon, 18 Sep 2000 11:09:53 -0700
- Cc: gdb-patches at sourceware dot cygnus dot com
- References: <1000621031433.ZM31859@ocotillo.lan> <39C6540B.1D3A2EC6@cygnus.com>
On Sep 18, 1:42pm, Andrew Cagney wrote:
> This change should be ok once Eli's concerns are addressed.
> Is that same (breakpoint moved) information included when doing an info
> breakpoints?
No. (At least not yet anyway.)
I took a look at this problem a week ago last weekend and concluded that
it was non-trivial to report the breakpoint-moved information. I forget
the exact details, but there are annotations to worry about plus the
fact that the breakpoint reporting code is ifdef'd in such a way that
we have two patches of code to worry about (UI_OUT vs non-UI_OUT).
Also, the way I was trying to get it reported...
Breakpoint 1 at 0x0620008c (adjusted from 0x6200090): file bar.c, line 21
was causing me to visit the frame reporting code which is outside of
breakpoint.c and this made me more than a little nervous. I'm going
to see if Eli's suggestion of formatting the information thusly
Breakpoint 1 at 0x0620008c: file bar.c, line 21
(breakpoint address adjusted from 0x6200090).
provides a more tenable solution.
The trick is finding time to do it.
Thanks for your feedback.
Kevin