This is the mail archive of the
mailing list for the libc-ports project.
Re: [PATCH] [AARCH64]: Pointer mangling support for Aarch64
- From: Tom Tromey <tromey at redhat dot com>
- To: Marcus Shawcroft <marcus dot shawcroft at gmail dot com>
- Cc: Venkataramanan Kumar <venkataramanan dot kumar at linaro dot org>, libc-ports at sourceware dot org, Patch Tracking <patch at linaro dot org>
- Date: Tue, 07 Jan 2014 11:10:12 -0700
- Subject: Re: [PATCH] [AARCH64]: Pointer mangling support for Aarch64
- Authentication-results: sourceware.org; auth=none
- References: <CAJK_mQ0EoE+_JQvSL+5=C_+Q6JgsV8hvXipy8OgR8+GYyYgt3A at mail dot gmail dot com> <87iotxm15i dot fsf at fleche dot redhat dot com> <CAJK_mQ2isVSQgbARrRT6KYGODUyCgAavnD-TTYVYK7_bUjb6LQ at mail dot gmail dot com> <CAFqB+Pzt2X9tcqCyzSBn0XcT62c09VUYikUHdNB6iuvrB8poWg at mail dot gmail dot com>
>>>>> "Marcus" == Marcus Shawcroft <firstname.lastname@example.org> writes:
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
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.