Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: palves@redhat.com, hjl.tools@gmail.com, gdb-patches@sourceware.org
Subject: Re: [7.5] PATCH: PR backtrace/14646 [x32] backtrace doesn't work
Date: Fri, 09 Nov 2012 16:54:00 -0000	[thread overview]
Message-ID: <20121109165339.GP5103@adacore.com> (raw)
In-Reply-To: <201211090958.qA99wlke004638@glazunov.sibelius.xs4all.nl>

> > only had effect on x32.
> 
> Yeah, it's pretty safe.  Must say that I don't see the urgency as x32
> is still in its infancy.

Thanks, guys. This takes care of my concerns regarding this patch.

-- 
Joel


  reply	other threads:[~2012-11-09 16:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-20 23:47 H.J. Lu
2012-10-21  1:56 ` Joel Brobecker
2012-10-21  2:06   ` H.J. Lu
2012-11-09  0:15   ` Pedro Alves
2012-11-09  9:59     ` Mark Kettenis
2012-11-09 16:54       ` Joel Brobecker [this message]
2012-11-10  0:53         ` H.J. Lu

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=20121109165339.GP5103@adacore.com \
    --to=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=hjl.tools@gmail.com \
    --cc=mark.kettenis@xs4all.nl \
    --cc=palves@redhat.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