Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Gabriel Krisman Bertazi <gabriel@krisman.be>
To: Sergio Durigan Junior <sergiodj@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFC PATCH 0/3] Catch syscall group
Date: Sun, 12 Oct 2014 21:12:00 -0000	[thread overview]
Message-ID: <8761fp6lhk.fsf@anubis.Home> (raw)
In-Reply-To: <87d2a2czjx.fsf@redhat.com> (Sergio Durigan Junior's message of	"Wed, 08 Oct 2014 12:10:42 -0400")

[-- Attachment #1: Type: text/plain, Size: 1421 bytes --]

Sergio Durigan Junior <sergiodj@redhat.com> writes:

> On Tuesday, October 07 2014, Gabriel Krisman Bertazi wrote:
>
>> Hello,
>>
>> This multi-part patch implements on top of the 'catch syscall' command
>> the ability to catch a group of related syscalls using a single
>> command.
>
Sergio and Doug,

Thank you both for your review.

>> (Please note that adding this feature to GDB was first suggested by Tom
>> Tromey on PR 15879. :-)
>>  <https://sourceware.org/bugzilla/show_bug.cgi?id=15879>).
>
> It is good to mention the bug in the ChangeLog, even if you are not
> directly fixing it.

Ok.

> I will make comments in the patch itself, but it would be nice if you
> could do that for the other existing XML files as well.  You didn't
> mention if you intend to do so or not.
>
> I know it will be kind of boring, but unfortunately those XML files are
> not being really maintained nowadays (a problem I intend to address soon
> with some patches and proposals), so if you don't touch those files now
> they will probably be forgotten for quite some time...
>
> However, this is just a request, so if you don't have the time to do
> that now I'd still vote for including this feature on GDB.

 I intend to do so for other architectures, but forgot to mention in my
original message.  Still, I won't be able to test on some platforms.

Thanks.

-- 
Gabriel Krisman Bertazi

[-- Attachment #2: Type: application/pgp-signature, Size: 818 bytes --]

  reply	other threads:[~2014-10-12 21:12 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-08  2:51 Gabriel Krisman Bertazi
2014-10-08  2:51 ` [RFC PATCH 1/3] Implemement support for groups of syscalls in the xml-syscall interface Gabriel Krisman Bertazi
2014-10-08 17:21   ` Sergio Durigan Junior
2014-10-08  2:51 ` [RFC PATCH 2/3] Add support to catch groups of syscalls Gabriel Krisman Bertazi
2014-10-08 19:07   ` Sergio Durigan Junior
2014-10-08 19:46     ` Doug Evans
2014-10-08 20:48       ` Sergio Durigan Junior
2014-10-12 21:37         ` Gabriel Krisman Bertazi
2014-10-12 22:52           ` Sergio Durigan Junior
2014-10-13 16:49           ` Doug Evans
2014-10-20  4:52             ` Gabriel Krisman Bertazi
2014-10-20 19:39               ` Sergio Durigan Junior
2014-10-27 19:20                 ` Doug Evans
2014-10-08  2:52 ` [RFC PATCH 3/3] Create syscall groups for x86_64 Gabriel Krisman Bertazi
2014-10-08 19:00   ` Sergio Durigan Junior
2014-10-08 16:10 ` [RFC PATCH 0/3] Catch syscall group Sergio Durigan Junior
2014-10-12 21:12   ` Gabriel Krisman Bertazi [this message]
2014-10-12 22:55     ` Sergio Durigan Junior
2014-10-08 16:12 ` Doug Evans

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=8761fp6lhk.fsf@anubis.Home \
    --to=gabriel@krisman.be \
    --cc=gdb-patches@sourceware.org \
    --cc=sergiodj@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