From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28769 invoked by alias); 10 Jan 2014 09:54:50 -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 28748 invoked by uid 89); 10 Jan 2014 09:54:49 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-0.8 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 X-HELO: mail-ie0-f174.google.com Received: from mail-ie0-f174.google.com (HELO mail-ie0-f174.google.com) (209.85.223.174) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES128-SHA encrypted) ESMTPS; Fri, 10 Jan 2014 09:54:48 +0000 Received: by mail-ie0-f174.google.com with SMTP id at1so4898795iec.33 for ; Fri, 10 Jan 2014 01:54:46 -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=ZWlN7/um6Wk7TrjbKC1cwYjjuq7f0Sm1251/bSk+yJ0=; b=QvX+76z0MEILiAbZ/QdOAdDzyb4Lcvi4B5sYLBv641X8mpA2iDTEwonZvUs1DJaAXO UPCGU6L+qXjdiuyDM3iz5EeKDSnOfMX1cql9XEtawSK5VesT09NSppAFQzHPcdVgqXH/ 4Oa2eKUGRxrEZ6CUfexMPRhBAO7QZgL6jUWraaQVMXJGaNm8HIq9d9EbrHHxQHyTfZ4x xWNYRj53Yg3M/IfTcg1z3pM7JUUESMtyMVLiw8l0psOoPWD78VU/0OcHFAxmGxm7Vg7c 90AmXYStFUnvUgKrF/Jk4Qxjx4uhAwHlswhSj8qbpI63i0wd5whxkayR3TSlMw5eDiuc wrcw== X-Gm-Message-State: ALoCoQnwwvwHJGRVYOFVQlCTQv+Pcxo3biwlpWY5LsrYM8SqLN18T9duANzPajj5ggBUjbqrgTRe MIME-Version: 1.0 X-Received: by 10.43.61.196 with SMTP id wx4mr7046414icb.6.1389347685844; Fri, 10 Jan 2014 01:54:45 -0800 (PST) Received: by 10.64.20.52 with HTTP; Fri, 10 Jan 2014 01:54:45 -0800 (PST) In-Reply-To: <87fvozhddn.fsf@fleche.redhat.com> References: <87iotxm15i.fsf@fleche.redhat.com> <87fvozhddn.fsf@fleche.redhat.com> Date: Fri, 10 Jan 2014 09:54: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/msg00029.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. Do you know if it is documented anywhere what the difference is between the longjmp and longjmp_target probes? It looks like on i386 the registers are restored in between longjmp/longjmp_target but on powerpc half the registers seem to have been restored by the time the longjmp probe is executed. AFAICT gdb does not use the longjmp_target probe either... Thanks, -- Will Newton Toolchain Working Group, Linaro