From: "Nan Xiao" <xiaonan19830818@qq.com>
To: "Doug Evans" <dje@google.com>
Cc: gdb <gdb@sourceware.org>
Subject: Re: Some questions about using gdb catch syscall function
Date: Tue, 09 Dec 2014 03:19:00 -0000 [thread overview]
Message-ID: <tencent_70C720E20ECE061354ED9A4E@qq.com> (raw)
In-Reply-To: <CADPb22S2X+KDghvq9RvBOiBF-ahuUKzm6s5PJ_stmTnvV9viFA@mail.gmail.com>
Hi Doug,
Thanks very much for your detailed and kindly explanations!
Per my understanding, if no "libexpat", "catch syscall" and "catch syscall number" still work normally, except some warnings. Right?
Best Regards
Nan Xiao
------------------ Original ------------------
From: "Doug Evans";<dje@google.com>;
Date: Tue, Dec 9, 2014 10:53 AM
To: "Nan Xiao"<xiaonan19830818@qq.com>;
Cc: "gdb"<gdb@sourceware.org>;
Subject: Re: Some questions about using gdb catch syscall function
On Mon, Dec 8, 2014 at 6:16 PM, Nan Xiao <xiaonan19830818@qq.com> wrote:
> Hi all,
>
> I am using gdb's catch syscall function(https://sourceware.org/gdb/onlinedocs/gdb/Set-Catchpoints.html#index-catch-syscall), and meets some issues. The procedure of running gdb is like this:
>
> (gdb) catch syscall
> warning: Can not parse XML syscalls information; XML support was disabled at compile time.
> Catchpoint 1 (any syscall)
> (gdb) catch syscall 1
> Catchpoint 2 (syscall 1)
> (gdb) catch syscall read
> Unknown syscall name 'read'.
>
> My questions are:
> (1) gdb prints "warning: Can not parse XML syscalls information; XML support was disabled at compile time.". Does it affect the normal use of catch function? It seems the gdb can set catchpoint normally.
You need to build gdb with "libexpat".
Check that you have it installed (I'm assuming not) and rebuild gdb.
If you have libexpat installed in a non-standard place, there are
options to gdb/configure to tell the build system where to find
libexpat.
bash$ gdb/configure --help # and grep for expat
>
> (2) I can use "catch syscall number" correctly, why can't use "catch syscall name"?
gdb uses libexpat to parse the xml descriptions of the syscalls, which
is how it knows their names.
No libexpat -> no ability to recognize syscall names.
>
> P.S., my gdb is 7.8.1 and runs on Linux X86.
>
> Could anyone give any comments about this issue? Thanks very much in advance!
>
> Best Regards
> Nan Xiao\x16º&ÖëzÛ«ýßÙb²Ö«r\x18\x1d
next prev parent reply other threads:[~2014-12-09 3:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-09 2:17 Nan Xiao
[not found] ` <CADPb22S2X+KDghvq9RvBOiBF-ahuUKzm6s5PJ_stmTnvV9viFA@mail.gmail.com>
2014-12-09 3:19 ` Nan Xiao [this message]
2014-12-09 19:45 ` Sergio Durigan Junior
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=tencent_70C720E20ECE061354ED9A4E@qq.com \
--to=xiaonan19830818@qq.com \
--cc=dje@google.com \
--cc=gdb@sourceware.org \
/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