From: "Monika Chaddha" <monika@acmet.com>
To: "'Dave Trollope'" <trollope@lucent.com>
Cc: "'Cuthbertson, Reva D.'" <reva_cuthbertson@hp.com>,
"'Daniel Jacobowitz'" <drow@false.org>, <gdb@sources.redhat.com>
Subject: RE: Question regarding setting breakpoints on 'C' labels and the handling of DW_TAG_label in new_symbol() in dwarf2read.c.
Date: Thu, 28 Jul 2005 06:13:00 -0000 [thread overview]
Message-ID: <005801c5933b$c7b74f00$5100a8c0@monika> (raw)
In-Reply-To: <42E85DC9.6040107@lucent.com>
I think that this can be achieved by putting breakpoints using function
names.
>-----Original Message-----
>From: gdb-owner@sources.redhat.com
[mailto:gdb-owner@sources.redhat.com] On
>Behalf Of Dave Trollope
>Sent: Thursday, July 28, 2005 9:54 AM
>To: Daniel Jacobowitz
>Cc: Cuthbertson, Reva D.; gdb@sources.redhat.com
>Subject: Re: Question regarding setting breakpoints on 'C' labels and
the
>handling of DW_TAG_label in new_symbol() in dwarf2read.c.
>
>
>I too tried this recently and was disappointed to find it didn't work.
>Heres why I was trying it:
>
>We have a number of source trees where code changes regularly. By using
>a label, we can write generic breakpoint scripts that are source tree
>independant (I.E. Don't need line numbers to place the breakpoint.
etc).
>
>Is there an alternative way to do what we are trying to achieve?
>
>Cheers
>Dave
>Daniel Jacobowitz wrote:
>
>>On Thu, Jun 23, 2005 at 04:56:15PM -0700, Cuthbertson, Reva D. wrote:
>>
>>
>>>Hello,
>>>
>>>I was trying to set a breakpoint on a 'C' label in gdb and when I
could
>>>not do it I tried to find out why. I noticed a few things and had a
few
>>>questions.
>>>
>>>
>>
>>Simply, GDB does not support this. It may have once upon a time, but
>>no one has used the feature for years.
>>
>>
>>
>>
next prev parent reply other threads:[~2005-07-28 6:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-23 23:57 Cuthbertson, Reva D.
2005-06-24 3:19 ` Daniel Jacobowitz
2005-07-28 4:24 ` Dave Trollope
2005-07-28 6:13 ` Monika Chaddha [this message]
2005-07-28 12:54 ` Daniel Jacobowitz
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='005801c5933b$c7b74f00$5100a8c0@monika' \
--to=monika@acmet.com \
--cc=drow@false.org \
--cc=gdb@sources.redhat.com \
--cc=reva_cuthbertson@hp.com \
--cc=trollope@lucent.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).