From: Sergio Durigan Junior <sergiodj@redhat.com>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 3/4 v3] Use longjmp and exception probes when available
Date: Fri, 27 Apr 2012 20:58:00 -0000 [thread overview]
Message-ID: <m31un8ao4v.fsf@redhat.com> (raw)
In-Reply-To: <87lilh2c60.fsf@fleche.redhat.com> (Tom Tromey's message of "Fri, 27 Apr 2012 13:43:35 -0600")
On Friday, April 27 2012, Tom Tromey wrote:
>>>>>> "Sergio" == Sergio Durigan Junior <sergiodj@redhat.com> writes:
>
> Sergio> This patch also almost didn't change from the first version.
> Sergio> http://sourceware.org/ml/gdb-patches/2012-03/msg00356.htmlSergio> OK to check-in?
>
> Yes, thanks.
Thanks, checked in:
http://sourceware.org/ml/gdb-cvs/2012-04/msg00228.html
--
Sergio
next prev parent reply other threads:[~2012-04-27 20:58 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-23 4:57 [PATCH 0/4 v3] Add support for static and SystemTap probes Sergio Durigan Junior
2012-04-23 4:59 ` [PATCH 3/4 v3] Use longjmp and exception probes when available Sergio Durigan Junior
2012-04-27 19:47 ` Tom Tromey
2012-04-27 20:58 ` Sergio Durigan Junior [this message]
2012-04-23 4:59 ` [PATCH 1/4 v3] Refactor internal variable mechanism Sergio Durigan Junior
2012-04-27 15:40 ` Tom Tromey
2012-04-27 20:57 ` Sergio Durigan Junior
2012-04-23 4:59 ` [PATCH 2/4 v3] Implement support for static and SystemTap probes Sergio Durigan Junior
2012-04-27 19:43 ` Tom Tromey
2012-04-27 20:58 ` Sergio Durigan Junior
2012-04-23 6:35 ` [PATCH 4/4 v3] Documentation and testsuite changes Sergio Durigan Junior
2012-04-27 19:58 ` Tom Tromey
2012-04-27 20:32 ` Tom Tromey
2012-04-27 20:57 ` Sergio Durigan Junior
2012-04-28 1:55 ` Sergio Durigan Junior
2012-04-28 23:30 ` Regression for gdb.trace/backtrace.exp [Re: [PATCH 0/4 v3] Add support for static and SystemTap probes] Jan Kratochvil
2012-04-29 6:29 ` Sergio Durigan Junior
2012-04-29 12:59 ` Jan Kratochvil
2012-04-29 18:03 ` Sergio Durigan Junior
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=m31un8ao4v.fsf@redhat.com \
--to=sergiodj@redhat.com \
--cc=gdb-patches@sourceware.org \
--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