From: Tom Tromey <tromey@redhat.com>
To: Marcus Shawcroft <marcus.shawcroft@gmail.com>
Cc: Venkataramanan Kumar <venkataramanan.kumar@linaro.org>,
libc-ports@sourceware.org,
Patch Tracking <patch@linaro.org>
Subject: Re: [PATCH] [AARCH64]: Pointer mangling support for Aarch64
Date: Tue, 07 Jan 2014 18:10:00 -0000 [thread overview]
Message-ID: <87fvozhddn.fsf@fleche.redhat.com> (raw)
In-Reply-To: <CAFqB+Pzt2X9tcqCyzSBn0XcT62c09VUYikUHdNB6iuvrB8poWg@mail.gmail.com> (Marcus Shawcroft's message of "Tue, 7 Jan 2014 12:17:06 +0000")
>>>>> "Marcus" == Marcus Shawcroft <marcus.shawcroft@gmail.com> 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
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.
Tom
next prev parent reply other threads:[~2014-01-07 18:10 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-26 12:25 Venkataramanan Kumar
2013-12-26 19:33 ` Richard Henderson
2013-12-27 7:48 ` Venkataramanan Kumar
2013-12-27 15:09 ` Richard Henderson
2013-12-30 5:00 ` Venkataramanan Kumar
2013-12-30 14:45 ` Richard Henderson
2013-12-30 15:36 ` Venkataramanan Kumar
2013-12-30 22:20 ` Marcus Shawcroft
2013-12-31 5:15 ` Venkataramanan Kumar
2014-01-01 17:42 ` Marcus Shawcroft
2014-01-06 18:11 ` Tom Tromey
2014-01-07 11:05 ` Venkataramanan Kumar
2014-01-07 12:17 ` Marcus Shawcroft
2014-01-07 18:10 ` Tom Tromey [this message]
2014-01-10 9:54 ` Will Newton
2014-01-20 9:01 ` Will Newton
2014-01-20 16:45 ` Tom Tromey
2014-01-20 17:02 ` Will Newton
2014-01-08 10:32 ` Venkataramanan Kumar
2014-01-10 10:40 ` Marcus Shawcroft
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87fvozhddn.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=libc-ports@sourceware.org \
--cc=marcus.shawcroft@gmail.com \
--cc=patch@linaro.org \
--cc=venkataramanan.kumar@linaro.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).