From: Tom Tromey <tromey@redhat.com>
To: jose.marchesi@oracle.com (Jose E. Marchesi)
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] [SPARC64] Figure out where a longjmp will land
Date: Tue, 08 Oct 2013 20:23:00 -0000 [thread overview]
Message-ID: <87d2nffr53.fsf@fleche.redhat.com> (raw)
In-Reply-To: <87y563k71b.fsf@oracle.com> (Jose E. Marchesi's message of "Tue, 08 Oct 2013 19:26:56 +0200")
>>>>> "Jose" == Jose E Marchesi <jose.marchesi@oracle.com> writes:
Jose> Note that in sparc64 glibc does not install probes in setjmp, nor it
Jose> mangles pointers.
In this case adding the probes is marginal; but you will probably want
to write the probe support for sparc64 in gdb anyway, because there are
other probes available that provide more noticeable benefits...
Jose> + return X_A(insn);
Space before the "(".
Someone else will have to do the real review though.
Tom
next prev parent reply other threads:[~2013-10-08 20:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-08 17:25 Jose E. Marchesi
2013-10-08 20:23 ` Tom Tromey [this message]
2013-10-08 20:49 ` Sergio Durigan Junior
2013-10-08 21:51 ` Jose E. Marchesi
2013-10-17 5:57 ` Joel Brobecker
2013-10-17 11:31 ` Jose E. Marchesi
2013-10-20 19:32 ` Mark Kettenis
2013-10-21 12:52 ` Jose E. Marchesi
2013-10-20 19:27 ` Mark Kettenis
2013-10-21 12:53 ` Jose E. Marchesi
2013-10-22 8:22 ` Mark Kettenis
2013-11-18 14:02 ` Jose E. Marchesi
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=87d2nffr53.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=jose.marchesi@oracle.com \
/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