Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Gabriel Krisman Bertazi <gabriel@krisman.be>
To: Doug Evans <dje@google.com>
Cc: gdb-patches@sourceware.org,  palves@redhat.com,  sergiodj@redhat.com
Subject: Re: [PATCH v5 4/5] Include group information to xml syscall files.
Date: Fri, 20 May 2016 02:30:00 -0000	[thread overview]
Message-ID: <87shxd1mx2.fsf@oberon.home> (raw)
In-Reply-To: <047d7b111fe189726f05330d0fb0@google.com> (Doug Evans's message	of "Tue, 17 May 2016 17:27:51 +0000")

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


Hey Doug,

> At the moment all group information comes from the defaults (I think).
> I'm assuming all one has to do for special cases is add the group(s)
> directly to the foo-xml.in file and that will work. Right?

Yes, it will (partially) work, but there is a limitation there.  You can
add groups for specific architectures directly in the <arch>.xml.in
file, but we don't allow appending more groups if there are some already
defined for that syscall in the linux-defaults file.  In other words,
appending more groups for a given syscall is not supported.  I didn't
see a need for that when I wrote it a while ago.

But this is a limitation, so I fixed that up in v6, which I'll post
soon after this email.

> IWBN to have some examples so people don't work from a default modus
> operandi
> of adding everything to linux-defaults.xml.in.

I didn't see the need nor have a good example for that now.. Do you have
a suggestion? Shouldn't we enforce it during review?

> btw, why is linux-defaults.xml.in a ".in" file?
> I'd expect it to just be linux-defaults.xml.

Because it won't be used directly, but serve as input to the xsl
pre-processor.

-- 
Gabriel Krisman Bertazi

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

  reply	other threads:[~2016-05-20  2:30 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-17 17:28 Doug Evans
2016-05-20  2:30 ` Gabriel Krisman Bertazi [this message]
2016-05-20  2:56   ` [PATCH v6 1/5] Implemement support for groups of syscalls in the xml-syscall interface Gabriel Krisman Bertazi
2016-05-20  2:56     ` [PATCH v6 3/5] Add tests for catching groups of syscalls on supported architectures Gabriel Krisman Bertazi
2016-05-26 18:18       ` Sergio Durigan Junior
2016-05-20  2:56     ` [PATCH v6 2/5] Add support to catch groups of syscalls Gabriel Krisman Bertazi
2016-05-26 18:17       ` Sergio Durigan Junior
2016-05-20  2:56     ` [PATCH v6 5/5] Update documentation on catching a group of related syscalls Gabriel Krisman Bertazi
2016-05-20  5:48       ` Eli Zaretskii
2016-05-26 18:22     ` [PATCH v6 1/5] Implemement support for groups of syscalls in the xml-syscall interface Sergio Durigan Junior
2016-05-20  3:10   ` [RESEND PATCH v6 4/5] Include group information to xml syscall files Gabriel Krisman Bertazi
2016-05-26 18:14     ` Sergio Durigan Junior
2016-05-27 10:18     ` Pedro Alves
2016-06-19 20:37       ` Gabriel Krisman Bertazi
  -- strict thread matches above, loose matches on Subject: below --
2016-05-15 20:32 [PATCH v5 0/5] Catch syscall groups Gabriel Krisman Bertazi
2016-05-15 20:32 ` [PATCH v5 4/5] Include group information to xml syscall files Gabriel Krisman Bertazi

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=87shxd1mx2.fsf@oberon.home \
    --to=gabriel@krisman.be \
    --cc=dje@google.com \
    --cc=gdb-patches@sourceware.org \
    --cc=palves@redhat.com \
    --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