From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-patches-return-120412-listarch-gdb-patches=sources.redhat.com@sourceware.org>
Received: (qmail 93284 invoked by alias); 3 Mar 2015 12:38:43 -0000
Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-patches.sourceware.org>
List-Subscribe: <mailto:gdb-patches-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-patches/>
List-Post: <mailto:gdb-patches@sourceware.org>
List-Help: <mailto:gdb-patches-help@sourceware.org>, <http://sourceware.org/ml/#faqs>
Sender: gdb-patches-owner@sourceware.org
Received: (qmail 93274 invoked by uid 89); 3 Mar 2015 12:38:43 -0000
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-2.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, 03 Mar 2015 12:38:39 +0000
Received: from int-mx13.intmail.prod.int.phx2.redhat.com (int-mx13.intmail.prod.int.phx2.redhat.com [10.5.11.26])	by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id t23CcbBt000911	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL);	Tue, 3 Mar 2015 07:38:37 -0500
Received: from [127.0.0.1] (ovpn01.gateway.prod.ext.ams2.redhat.com [10.39.146.11])	by int-mx13.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id t23CcZst017224;	Tue, 3 Mar 2015 07:38:36 -0500
Message-ID: <54F5AB4A.9080206@redhat.com>
Date: Tue, 03 Mar 2015 12:38:00 -0000
From: Pedro Alves <palves@redhat.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.3.0
MIME-Version: 1.0
To: Yao Qi <qiyaoltc@gmail.com>
CC: 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>	<54F0BC6B.8070901@redhat.com> <86pp8qi8ui.fsf@gmail.com>
In-Reply-To: <86pp8qi8ui.fsf@gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-SW-Source: 2015-03/txt/msg00076.txt.bz2

On 03/03/2015 12:06 PM, Yao Qi wrote:
> Pedro Alves <palves@redhat.com> writes:
> 
>> Do we actually need to do anything when the inferior is created?
>> Supposedly once the inferior is created, we'll try to insert
>> the catchpoint, and that will fail is the target does not
>> support it.
> 
> No, but we need to tweak test case to emit UNSUPPORTED instead of FAIL
> if the target doesn't support "catch syscall".

Yeah, I'm imagining that we'll just detect it like we detect failures
to insert hardware breakpoints / watchpoints, at resume time.
Something like:

    set test "continue with catch syscall"
    gdb_test_multiple "continue" $test {
	-re "Could not insert syscall catchpoint.*$gdb_prompt $" {
              ...
	}
	-re "Breakpoint .*$gdb_prompt $" {
              ...
	}
    }

Thanks,
Pedro Alves