From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 31262 invoked by alias); 20 Jan 2014 09:01:01 -0000 Mailing-List: contact libc-ports-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: libc-ports-owner@sourceware.org Received: (qmail 31240 invoked by uid 89); 20 Jan 2014 09:01:00 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.0 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 X-HELO: mail-ie0-f173.google.com Received: from mail-ie0-f173.google.com (HELO mail-ie0-f173.google.com) (209.85.223.173) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES128-SHA encrypted) ESMTPS; Mon, 20 Jan 2014 09:00:59 +0000 Received: by mail-ie0-f173.google.com with SMTP id e14so7933182iej.4 for ; Mon, 20 Jan 2014 01:00:58 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=i5NsukQxBcFBq1/WeNT9UG7SCJw/zx9ts4q87pDTG38=; b=YBukEa70VH5oPQIp/pXPfRZX6U99SBbvQbgr6lfW+ToN65vasMjo3tJ6gq0ZsWBare 36HxwxYW17VdvhLdN0hq84YxPw0aWYHqwapR5DiSrp5wtwk2MPgdy7r6mtjh0XJHA5R1 TpUcWNeGvGVlpXImsawjD9d6vxNzAL7KDRMAxXZdgBOL1b8jye03esnuEy1tASwJCuTx pJp1lDohKfleK7hSaePlqgzrohLQ5SqRw9tZRlWmqzizaT0GNLTMlI/K6JdmS1GQ8mJl 8A60eHgbGFI7J/Su8PR7rxkxSGLnAqbe8lyiUCuB+BTTW+LUxCdUm4DZEKWKhaLLNCaD 4GIw== X-Gm-Message-State: ALoCoQnKDcKDOxm36L8hQg/vnsCweWkRwG0fVccH/sOj1TcHNLrjvcafNkpK0MVrAYp+hVU2oQBE MIME-Version: 1.0 X-Received: by 10.50.79.198 with SMTP id l6mr11160415igx.23.1390208458062; Mon, 20 Jan 2014 01:00:58 -0800 (PST) Received: by 10.64.20.52 with HTTP; Mon, 20 Jan 2014 01:00:57 -0800 (PST) In-Reply-To: <87fvozhddn.fsf@fleche.redhat.com> References: <87iotxm15i.fsf@fleche.redhat.com> <87fvozhddn.fsf@fleche.redhat.com> Date: Mon, 20 Jan 2014 09:01:00 -0000 Message-ID: Subject: Re: [PATCH] [AARCH64]: Pointer mangling support for Aarch64 From: Will Newton To: Tom Tromey Cc: Marcus Shawcroft , Venkataramanan Kumar , "libc-ports@sourceware.org" , Patch Tracking Content-Type: text/plain; charset=ISO-8859-1 X-IsSubscribed: yes X-SW-Source: 2014-01/txt/msg00037.txt.bz2 On 7 January 2014 18:10, Tom Tromey wrote: Hi Tom, > Marcus> Hi, I'm not familiar with the inner workings of STAP probes, can you > Marcus> explain what the arguments of longjmp_target should be at a semantic > Marcus> level rather than the proposed location to get the values from? > > I was going to say manual/probes.texi but I see the longjmp probes > aren't documented. > > Currently gdb only uses the third argument, which is the target PC. > > Marcus> Do we need probes in setjmp aswell? > > I think it's nice for users if the probes are the same across ports. > > That said, gdb itself only uses the longjmp and rtld probes from glibc. > gdb users (or SystemTap users) can refer to the other probes though. Can you confirm that gdb does not use the longjmp_target probe? It doesn't appear to use it as far as I can tell. Are you aware of what consumers there are for this probe point? Thanks, -- Will Newton Toolchain Working Group, Linaro