This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
Re: Some questions about using gdb catch syscall function
- From: Sergio Durigan Junior <sergiodj at redhat dot com>
- To: "Nan Xiao" <xiaonan19830818 at qq dot com>
- Cc: "Doug Evans" <dje at google dot com>, "gdb" <gdb at sourceware dot org>
- Date: Tue, 09 Dec 2014 13:51:08 -0500
- Subject: Re: Some questions about using gdb catch syscall function
- Authentication-results: sourceware.org; auth=none
- References: <tencent_2AE9A6F86BC6AEB6020750A9 at qq dot com> <CADPb22S2X+KDghvq9RvBOiBF-ahuUKzm6s5PJ_stmTnvV9viFA at mail dot gmail dot com> <tencent_70C720E20ECE061354ED9A4E at qq dot com>
On Monday, December 08 2014, Nan Xiao wrote:
> Per my understanding, if no "libexpat", "catch syscall" and "catch syscall number" still work normally, except some warnings. Right?
Yes, it should work normally. The testcase for catch-syscall even tests
this scenario. But as Doug said, you will only be able to use/see
syscall numbers, not their names.
--
Sergio
GPG key ID: 0x65FC5E36
Please send encrypted e-mail if possible
http://sergiodj.net/