From: "Douglas Evans" <dje@google.com>
To: gdb-patches@sourceware.org
Subject: Re: RFA: patch to fix multi-breakpoint enable/disable handling of inline functions
Date: Mon, 05 Nov 2007 20:06:00 -0000 [thread overview]
Message-ID: <e394668d0711051206x1bc0febaj96f12157be0373d4@mail.gmail.com> (raw)
In-Reply-To: <20071022212517.GA23401@caradoc.them.org>
On Oct 22, 2007 2:25 PM, Daniel Jacobowitz <drow@false.org> wrote:
> On Mon, Oct 22, 2007 at 02:22:31PM -0700, Douglas Evans wrote:
> > Ping.
> >
> > I've split the patch into two parts, separating out the tweaks to
> > mb-templates.exp,mb-ctor.exp (I'll send this in a separate message).
> > I also fixed a few typos. The revised patch is attached.
> >
> > Ok to check in?
>
> I've been hoping Vladimir would look at this - Vladimir?
>
> If he doesn't have time I'll try to figure it out.
The bug is that transferring enable/disable status from the old
breakpoint list to the new one (which is done each time the program is
run) gets the wrong results for static inline functions with
multi-breakpoints. In my testcase 1.1 is enabled and 1.2 is disabled,
but when the program is run 1.1 becomes disabled and 1.2 becomes
enabled. The code uses strcmp to distinguish the functions but
clearly that can't work in this case. The patch adds code to
recognize this case of ambiguous function names and when detected uses
the pc address instead. Using the pc address is less preferable to
strcmp because if the user changes the program, functions can move,
but in this case strcmp doesn't work at all. OTOH the patch is simple
and gets the right answer most of the time. More complex solutions
are possible - I'd still add this patch until then, but that's just my
$0.02.
next prev parent reply other threads:[~2007-11-05 20:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-16 4:12 Doug Evans
2007-10-22 21:25 ` Douglas Evans
2007-10-22 21:26 ` Daniel Jacobowitz
2007-11-05 20:06 ` Douglas Evans [this message]
2007-11-13 21:10 ` Vladimir Prus
2007-11-14 22:25 ` Douglas Evans
2007-11-14 22:49 ` Douglas Evans
2007-11-26 23:22 ` Douglas Evans
2007-12-21 18:04 ` Doug Evans
2007-12-27 19:20 ` Vladimir Prus
2008-01-28 18:17 ` Doug Evans
2008-02-06 19:09 ` Doug Evans
2008-02-06 19:16 ` Daniel Jacobowitz
2008-02-06 19:25 ` 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=e394668d0711051206x1bc0febaj96f12157be0373d4@mail.gmail.com \
--to=dje@google.com \
--cc=gdb-patches@sourceware.org \
/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