From: Paul Pluzhnikov <ppluzhnikov@google.com>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb-patches@sourceware.org, Jan Kratochvil <jan.kratochvil@redhat.com>
Subject: Re: [patch] Fix for PR gdb/12573
Date: Fri, 18 Mar 2011 18:28:00 -0000 [thread overview]
Message-ID: <AANLkTikd4z=B3VeU1f_gqXxKOL9VLAdv7Ba5HQtu5uZ4@mail.gmail.com> (raw)
In-Reply-To: <m38vwcxugq.fsf@fleche.redhat.com>
On Fri, Mar 18, 2011 at 9:29 AM, Tom Tromey <tromey@redhat.com> wrote:
>>>>>> "Paul" == Paul Pluzhnikov <ppluzhnikov@google.com> writes:
>
> Paul> Attached patch fixes http://sourceware.org/bugzilla/show_bug.cgi?id=12573
> Paul> by removing (I believe incorrect) assertion.
>
> See also:
>
> https://bugzilla.redhat.com/show_bug.cgi?id=612253
>
> And Jan's patch:
>
> http://sourceware.org/ml/gdb-patches/2010-07/msg00533.html
>
> I can't say I fully understand Jan's.
The patch looks good to me (and I *think* I understand it).
> It includes yours, though, and comes with a test case.
I was going to include a test case when pinging my patch in a week ;-)
Jan,
Could you reference PR gdb/12573 in your patch, and maybe commit it?
+ /* Place breakpoint only to the first PC in a function, even if some of
+ them are in a lexical sub-block. Put it too all the function
+ instances incl. the inlined ones. */
Suggest:
Put it on all function instances as well, including inlined ones.
Thanks,
--
Paul Pluzhnikov
next prev parent reply other threads:[~2011-03-18 17:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-17 6:43 Paul Pluzhnikov
2011-03-18 17:13 ` Tom Tromey
2011-03-18 18:28 ` Paul Pluzhnikov [this message]
2011-03-18 18:28 ` Jan Kratochvil
2011-03-28 17:11 ` [patch] Do not skip prologue for -O2 -g with GCC VTA " Jan Kratochvil
2011-04-11 18:26 ` Paul Pluzhnikov
2011-04-15 20:19 ` obsolete: " Jan Kratochvil
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='AANLkTikd4z=B3VeU1f_gqXxKOL9VLAdv7Ba5HQtu5uZ4@mail.gmail.com' \
--to=ppluzhnikov@google.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=tromey@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