Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: teawater <teawater@gmail.com>
To: "Sérgio Durigan Júnior" <sergiodj@linux.vnet.ibm.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 0/4] catch syscall -- try 4 -- Introduction
Date: Mon, 02 Feb 2009 13:01:00 -0000	[thread overview]
Message-ID: <daef60380902020501w46438316mb2b6b1ec46e5c6dd@mail.gmail.com> (raw)
In-Reply-To: <1232929826.26873.21.camel@miki>

Hi Sérgio,

I try it and I think it's so great.

When I use it, I got:
(gdb) catch syscall
warning: Can not parse XML syscalls information; XML support was
disabled at compile time
warning: Could not load the syscall XML file 'syscalls/i386-linux.xml'.
GDB will not be able to display syscall names.
Catchpoint 2 (any syscall)

Does it have some interface to set directory of xml file with myself?
I saw the texinfo but didn't get anything about it.

Thanks,
Hui

On Mon, Jan 26, 2009 at 08:30, Sérgio Durigan Júnior
<sergiodj@linux.vnet.ibm.com> wrote:
> Hello everybody,
>
> It's been a while since I don't post anything related to this patch, so
> I apologize. I've been busy with some other activities, so I had to use
> my spare time to work on this now.
>
> Here goes the fourth version of the catch syscall patch. For those of
> you who have been following the improvements, there's not so much to see
> in this version if you compare it to the previous one; even though, it's
> worth taking a look at it because there are lots of bug fixes (the vast
> majority were fixed by Jan K. , to whom I'd like to give my special
> thanks). The basic functionality remains the same.
>
> Many thanks to Jan K., Phil Muldoon, Rick Moseley and Tom Tromey for
> dedicating their time to this activity. Also, thanks to teawater and
> Daniel Jacobowitz for bringing this patch back to discussion.
>
> The division of the patch is basically the same: the first part contains
> architecture-independent code; the second contains
> architecture-dependent; the third is for the XML support code; and the
> fourth contains code for the build system, testacase and documentation.
> Please, apply all four patches in order to have GDB compiled correctly.
>
> Please, comment, test and review.
>
> Regards,
>
> --
> Sérgio Durigan Júnior
> Linux on Power Toolchain - Software Engineer
> Linux Technology Center - LTC
> IBM Brazil
>
>


  reply	other threads:[~2009-02-02 13:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-26  0:30 Sérgio Durigan Júnior
2009-02-02 13:01 ` teawater [this message]
2009-02-02 17:04   ` Daniel Jacobowitz
2009-02-03  3:20     ` teawater
2009-02-12  7:16 ` teawater

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=daef60380902020501w46438316mb2b6b1ec46e5c6dd@mail.gmail.com \
    --to=teawater@gmail.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