From: Kevin Buettner <kevinb@redhat.com>
To: Andrew Cagney <ac131313@redhat.com>, Kevin Buettner <kevinb@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [patch, rfa:ppc64, rfa:breakpoint] Add non-verbose breakpoint adjustment
Date: Wed, 29 Oct 2003 16:30:00 -0000 [thread overview]
Message-ID: <1031029163018.ZM6880@localhost.localdomain> (raw)
In-Reply-To: Andrew Cagney <ac131313@redhat.com> "Re: [patch, rfa:ppc64, rfa:breakpoint] Add non-verbose breakpoint adjustment" (Oct 28, 11:08am)
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
next prev parent reply other threads:[~2003-10-29 16:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-28 17:41 Andrew Cagney
2003-10-28 20:59 ` Kevin Buettner
2003-10-28 23:39 ` Andrew Cagney
2003-10-29 3:27 ` Kevin Buettner
2003-10-29 16:09 ` Andrew Cagney
2003-10-29 16:30 ` Kevin Buettner [this message]
2003-10-29 22:03 ` Andrew Cagney
2003-10-30 23:29 ` Kevin Buettner
2003-10-31 16:39 ` Andrew Cagney
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1031029163018.ZM6880@localhost.localdomain \
--to=kevinb@redhat.com \
--cc=ac131313@redhat.com \
--cc=gdb-patches@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox