From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8635 invoked by alias); 9 Dec 2014 19:45:55 -0000 Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org Received: (qmail 8625 invoked by uid 89); 9 Dec 2014 19:45:54 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-3.0 required=5.0 tests=AWL,BAYES_00,SPF_HELO_PASS,SPF_PASS,T_RP_MATCHES_RCVD autolearn=ham version=3.3.2 X-HELO: mx1.redhat.com Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-GCM-SHA384 encrypted) ESMTPS; Tue, 09 Dec 2014 19:45:52 +0000 Received: from int-mx09.intmail.prod.int.phx2.redhat.com (int-mx09.intmail.prod.int.phx2.redhat.com [10.5.11.22]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id sB9Jjg6J010195 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL); Tue, 9 Dec 2014 14:45:46 -0500 Received: from localhost (dhcp-10-15-16-169.yyz.redhat.com [10.15.16.169]) by int-mx09.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id sB9Ip9O2031799 (version=TLSv1/SSLv3 cipher=AES128-GCM-SHA256 bits=128 verify=NO); Tue, 9 Dec 2014 13:51:09 -0500 From: Sergio Durigan Junior To: "Nan Xiao" Cc: "Doug Evans" , "gdb" Subject: Re: Some questions about using gdb catch syscall function References: X-URL: http://blog.sergiodj.net Date: Tue, 09 Dec 2014 19:45:00 -0000 In-Reply-To: (Nan Xiao's message of "Tue, 9 Dec 2014 11:18:49 +0800") Message-ID: <877fy0irmr.fsf@redhat.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-IsSubscribed: yes X-SW-Source: 2014-12/txt/msg00017.txt.bz2 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/