From: "Ulrich Weigand" <uweigand@de.ibm.com>
To: pedro@codesourcery.com (Pedro Alves)
Cc: gdb-patches@sourceware.org, tromey@redhat.com
Subject: Re: [rfc] longjmp breakpoints (Re: [00/19] Eliminate some more current_gdbarch uses)
Date: Wed, 24 Jun 2009 16:44:00 -0000 [thread overview]
Message-ID: <200906241643.n5OGhuxw027407@d12av02.megacenter.de.ibm.com> (raw)
In-Reply-To: <200906241603.34227.pedro@codesourcery.com> from "Pedro Alves" at Jun 24, 2009 04:03:33 PM
Pedro Alves wrote:
> > This patch implements the idea of maintaining "master copies" of the
> > longjmp breakpoints that are created at the same places where overlay
> > event breakpoints are created today, and then installing momentary
> > clones while we want them to be active within a thread.
> >
> > What do you think?
>
> Looks good to me. Thanks!
Thanks for the review!
I've noticed the patch as posted as a silly bug:
> > + ALL_BREAKPOINTS_SAFE (b, temp)
> > + if (b->type == bp_longjmp_master)
> > + {
> > + struct breakpoint *clone = clone_momentary_breakpoint (b);
> > + b->type = bp_longjmp;
> > + b->thread = thread;
> > + }
This obviously needs to set clone->type and clone->thread instead.
I've now re-tested and checked in the fixed version.
Bye,
Ulrich
--
Dr. Ulrich Weigand
GNU Toolchain for Linux on System z and Cell BE
Ulrich.Weigand@de.ibm.com
next prev parent reply other threads:[~2009-06-24 16:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-05 21:13 [00/19] Eliminate some more current_gdbarch uses Ulrich Weigand
2009-06-05 22:24 ` Pedro Alves
2009-06-05 22:54 ` Tom Tromey
2009-06-05 23:30 ` Pedro Alves
2009-06-08 14:38 ` Ulrich Weigand
2009-06-08 14:48 ` Pedro Alves
2009-06-23 18:04 ` [rfc] longjmp breakpoints (Re: [00/19] Eliminate some more current_gdbarch uses) Ulrich Weigand
2009-06-24 15:02 ` Pedro Alves
2009-06-24 16:44 ` Ulrich Weigand [this message]
2009-06-17 18:58 ` [00/19] Eliminate some more current_gdbarch uses Ulrich Weigand
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=200906241643.n5OGhuxw027407@d12av02.megacenter.de.ibm.com \
--to=uweigand@de.ibm.com \
--cc=gdb-patches@sourceware.org \
--cc=pedro@codesourcery.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