From: Tom Tromey <tromey@redhat.com>
To: Michael Snyder <msnyder@vmware.com>
Cc: "gdb-patches\@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: RFC: allow breakpoints on labels
Date: Fri, 21 Aug 2009 22:16:00 -0000 [thread overview]
Message-ID: <m3my5s24rg.fsf@fleche.redhat.com> (raw)
In-Reply-To: <4A8D8A26.7010303@vmware.com> (Michael Snyder's message of "Thu, 20 Aug 2009 10:38:46 -0700")
>>>>> "Michael" == Michael Snyder <msnyder@vmware.com> writes:
Michael> 1) Labels will be in a separate name-space from other symbols
Michael> (functions)?
Yes. Here I just reused some existing gdb infrastructure, which appears
to mostly be unused.
You can't even "print label" at the moment, due to this.
It might be nice to implement the GCC address-of-label extension, though
this doesn't seem to be extremely useful.
Michael> 2) The search order will find functions first, and only if
Michael> there is no conflicting function, find a label? What if
Michael> there's a function and a label of the same name, and user
Michael> wants to specify the label?
Yes, functions are searched first. There's no way to pick the label in
this case.
Michael> 3) There's no danger of our confusing a label with a
Michael> function somewhere downstream, and doing something silly
Michael> such as applying prologue_skip or skip_trampoline to a label?
I don't think so, but I'm really not sure how I would be sure.
Tom
next prev parent reply other threads:[~2009-08-21 22:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-20 17:42 Tom Tromey
2009-08-20 17:58 ` Michael Snyder
2009-08-21 22:16 ` Tom Tromey [this message]
2009-08-20 20:40 ` Eli Zaretskii
2009-08-22 10:21 ` Tom Tromey
2010-07-13 19:26 ` Tom Tromey
2010-07-13 20:07 ` Tom Tromey
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=m3my5s24rg.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=msnyder@vmware.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