From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 127050 invoked by alias); 3 Mar 2015 18:06:18 -0000 Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org Received: (qmail 127040 invoked by uid 89); 3 Mar 2015 18:06:18 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.8 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, 03 Mar 2015 18:06:17 +0000 Received: from int-mx14.intmail.prod.int.phx2.redhat.com (int-mx14.intmail.prod.int.phx2.redhat.com [10.5.11.27]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id t23I6ESh005839 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL); Tue, 3 Mar 2015 13:06:14 -0500 Received: from localhost (dhcp-10-15-16-169.yyz.redhat.com [10.15.16.169]) by int-mx14.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id t23I6EiE026448 (version=TLSv1/SSLv3 cipher=AES128-GCM-SHA256 bits=128 verify=NO); Tue, 3 Mar 2015 13:06:14 -0500 From: Sergio Durigan Junior To: Pedro Alves Cc: Yao Qi , gdb-patches@sourceware.org Subject: Re: [RFC] Support command "catch syscall" properly on different targets References: <1425047015-1906-1-git-send-email-qiyaoltc@gmail.com> <877fv3kqx1.fsf@redhat.com> <86lhjei8md.fsf@gmail.com> <54F5A90E.8050704@redhat.com> X-URL: http://blog.sergiodj.net Date: Tue, 03 Mar 2015 18:06:00 -0000 In-Reply-To: <54F5A90E.8050704@redhat.com> (Pedro Alves's message of "Tue, 03 Mar 2015 12:29:02 +0000") Message-ID: <87bnkaklbe.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: 2015-03/txt/msg00107.txt.bz2 On Tuesday, March 03 2015, Pedro Alves wrote: > On 03/03/2015 12:11 PM, Yao Qi wrote: >> Sergio Durigan Junior writes: >> >>> You mean it's possible to use "catch syscall" on HP-UX targets? I >>> wonder how it works. >> >> Yes, that is what I meant, at least that is what I can tell from the >> source. > > TARGET_WAITKIND_SYSCALL_ENTRY / TARGET_WAITKIND_SYSCALL_RETURN > was supported by the HP-UX target long before GNU/Linux gained > support. See inf-ttrace.c. However, I don't think "catch syscall" > itself ever did. inf_ttrace_enable_syscall_events is only used > for watchpoints. Not that I find we should go fix it, mind you. Exactly, that's what I meant by my question. Sorry for not being clear. I remember seeing TARGET_WAITKIND_SYSCALL_{ENTRY,RETURN} when implementing "catch syscall", and I even remember making a decision to use them instead of creating other TARGET_WAITKIND's. However, the "catch syscall" itself doesn't work on HP-UX. Anyway, I just raised this point because we shouldn't "return 1" when asked if inf-ttrace.c supports "catch syscall". -- Sergio GPG key ID: 0x65FC5E36 Please send encrypted e-mail if possible http://sergiodj.net/