From: Daniel Jacobowitz <dan@codesourcery.com>
To: Pedro Alves <pedro@codesourcery.com>
Cc: gdb-patches@sourceware.org, Tom Tromey <tromey@redhat.com>
Subject: Re: RFC: change needs_frame_tls_address
Date: Mon, 26 Jul 2010 13:36:00 -0000 [thread overview]
Message-ID: <20100726133630.GA18091@caradoc.them.org> (raw)
In-Reply-To: <201007240204.20661.pedro@codesourcery.com>
On Sat, Jul 24, 2010 at 02:04:20AM +0100, Pedro Alves wrote:
> Given that if you have registers, you always have a frame, I don't
> think that's a good check.
Agreed. Do we need to separate "needs any frame" vs "specific to one
frame" if parts of GDB ask both questions? This is the same as a
global register variable - which I'm sure GDB messes up too :-)
--
Daniel Jacobowitz
CodeSourcery
prev parent reply other threads:[~2010-07-26 13:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-23 22:33 Tom Tromey
2010-07-24 1:04 ` Pedro Alves
2010-07-26 13:36 ` Daniel Jacobowitz [this message]
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=20100726133630.GA18091@caradoc.them.org \
--to=dan@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=pedro@codesourcery.com \
--cc=tromey@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