This is the mail archive of the
gdb-patches@sources.redhat.com
mailing list for the GDB project.
Re: [patch, rfa:ppc64, rfa:breakpoint] Add non-verbose breakpoint adjustment
On Oct 28, 11:08am, Andrew Cagney wrote:
> > As a user, it annoyed me :-)
> >>
> >> If you'd prefer I'll let PPC64 print both warnings as well.
> >
> > ppc and frv are very different.
>
> I'm not so sure. Here's the interaction:
>
> (gdb) print &main
> $1 = (<data variable, no debug info> *) 0x104e5a60
> (gdb) break main
> Breakpoint 2 at 0x100895d0
> (gdb) run
> Starting program:
> /home/cagney/PENDING/YYYY-MM-DD-target-convert-func/64/gdb/stripped.gdb
> ...
> Breakpoint 2, 0x00000000100895d0 in .main ()
> (gdb)
>
> (I've yet to figure out why GDB keeps reporting those breakpoints).
??
> Notice how "main" is in the data space yet GDB set a code space
> breakpoint (and even stopped on a different symbol). Might as well
> notify the user of this adjustment.
Okay, I see your point. This is surprising enough to merit a warning.
Kevin
- References:
- [patch, rfa:ppc64, rfa:breakpoint] Add non-verbose breakpoint adjustment
- Re: [patch, rfa:ppc64, rfa:breakpoint] Add non-verbose breakpoint adjustment
- Re: [patch, rfa:ppc64, rfa:breakpoint] Add non-verbose breakpointadjustment
- Re: [patch, rfa:ppc64, rfa:breakpoint] Add non-verbose breakpoint adjustment
- Re: [patch, rfa:ppc64, rfa:breakpoint] Add non-verbose breakpointadjustment