From: Tom Tromey <tromey@redhat.com>
To: "Sérgio Durigan Júnior" <sergiodj@linux.vnet.ibm.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 3/4] 'catch syscall' feature -- XML support part
Date: Fri, 07 Nov 2008 18:24:00 -0000 [thread overview]
Message-ID: <m37i7f8ke2.fsf@fleche.redhat.com> (raw)
In-Reply-To: <1226029557.32321.104.camel@miki> (=?utf-8?Q?=22S=C3=A9rgio?= Durigan =?utf-8?Q?J=C3=BAnior=22's?= message of "Fri\, 07 Nov 2008 01\:45\:57 -0200")
>>>>> "Sérgio" == Sérgio Durigan Júnior <sergiodj@linux.vnet.ibm.com> writes:
Tom> This will make an entry with an empty name given the above XML
Tom> snippet. But that doesn't seem helpful... if this triggers, won't it
Tom> print as an unnamed syscall? It seems to me that it would be
Tom> preferable to skip nameless ones and just report them numerically, if
Tom> they occur.
Sérgio> I'm sorry, but I think I didn't understand completely what you
Sérgio> suggested. You mean that I should set the syscall name to NULL when
Sérgio> there's no name for it in the XML file?
I think nameless syscalls should simply not be in the table at all.
Sérgio> + if (gdb_xml_parse (parser, document) == 0)
Sérgio> + {
Sérgio> + /* Parsed successfully. */
Sérgio> + discard_cleanups (result_cleanup);
Sérgio> + do_cleanups (back_to);
Sérgio> + return data.sysinfo;
Sérgio> + }
Sérgio> + else
Sérgio> + {
Sérgio> + warning (_("Could not load XML syscalls info; ignoring"));
Sérgio> + do_cleanups (back_to);
Sérgio> + return NULL;
Tom>
Tom> ... you can either just do_ or discard_ result_cleanup instead.
Sérgio> I'm sorry, instead of what? do_cleanups? :-)
I think instead of the above you can simply:
if (...)
...
discard_cleanups (result_cleanup);
else
...
do_cleanups (result_cleanup);
Tom
next prev parent reply other threads:[~2008-11-07 18:24 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-04 4:32 Sérgio Durigan Júnior
2008-11-04 13:36 ` Mark Kettenis
2008-11-04 13:47 ` Daniel Jacobowitz
2008-11-04 15:05 ` Sérgio Durigan Júnior
2008-11-04 15:13 ` Daniel Jacobowitz
2008-11-04 15:18 ` Sérgio Durigan Júnior
2008-11-04 15:06 ` Sérgio Durigan Júnior
2008-11-08 19:06 ` Mark Kettenis
2008-11-04 18:41 ` Tom Tromey
2008-11-07 3:46 ` Sérgio Durigan Júnior
2008-11-07 18:24 ` Tom Tromey [this message]
2008-11-04 21:20 ` Eli Zaretskii
2008-11-04 22:23 ` Daniel Jacobowitz
2008-11-04 22:27 ` Eli Zaretskii
2008-11-04 22:36 ` Daniel Jacobowitz
2008-11-05 1:02 ` Sérgio Durigan Júnior
2008-11-05 4:22 ` Eli Zaretskii
2008-11-05 14:57 ` Daniel Jacobowitz
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=m37i7f8ke2.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=sergiodj@linux.vnet.ibm.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