From: Sergio Durigan Junior <sergiodj@redhat.com>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: gdb-patches@sourceware.org, brobecker@adacore.com
Subject: Re: [PATCH] Fix for PR tdep/16397: SystemTap SDT probe support for x86 doesn't work with "triplet operands"
Date: Thu, 20 Feb 2014 21:53:00 -0000 [thread overview]
Message-ID: <m3y515pi26.fsf@redhat.com> (raw)
In-Reply-To: <201401301535.s0UFZp3N013895@glazunov.sibelius.xs4all.nl> (Mark Kettenis's message of "Thu, 30 Jan 2014 16:35:51 +0100 (CET)")
On Thursday, January 30 2014, Mark Kettenis wrote:
>> From: Sergio Durigan Junior <sergiodj@redhat.com>
>> Date: Thu, 30 Jan 2014 13:16:15 -0200
>>
>> On Friday, January 17 2014, I wrote:
>>
>> > On Sunday, January 12 2014, I wrote:
>> >
>> >> Hi,
>> >>
>> >> This is the continuation of what Joel proposed on:
>> >>
>> >> <https://sourceware.org/ml/gdb-patches/2013-12/msg00977.html>
>> >
>> > Ping.
>>
>> Ping^2.
>
> No objection to this going in (other than the unsafe use of
> isdigit(3)) but I don't claim to know wnything of the SDT stuff.
Thanks, I finally pushed it with the necessary fixes.
https://sourceware.org/ml/gdb-cvs/2014-02/msg00106.html
--
Sergio
next prev parent reply other threads:[~2014-02-20 21:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-12 4:06 Sergio Durigan Junior
2014-01-17 21:31 ` Sergio Durigan Junior
2014-01-30 15:16 ` Sergio Durigan Junior
2014-01-30 15:36 ` Mark Kettenis
2014-02-02 16:29 ` Sergio Durigan Junior
2014-02-02 17:07 ` Mark Kettenis
2014-02-20 21:53 ` Sergio Durigan Junior [this message]
2014-06-22 21:14 ` [testsuite patch+7.8] gdb.arch/amd64-stap-special-operands.exp !is_lp64_target [Re: [PATCH] Fix for PR tdep/16397: SystemTap SDT probe support for x86 doesn't work with "triplet operands"] Jan Kratochvil
2014-06-22 22:17 ` Sergio Durigan Junior
2014-06-23 6:30 ` [testsuite obv+7.8] " 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=m3y515pi26.fsf@redhat.com \
--to=sergiodj@redhat.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=mark.kettenis@xs4all.nl \
/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).