From: Joel Brobecker <brobecker@adacore.com>
To: Pedro Alves <pedro@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA/RFC] Restore old handling of multi-register variables
Date: Thu, 06 Oct 2011 20:11:00 -0000 [thread overview]
Message-ID: <20111006201053.GS19246@adacore.com> (raw)
In-Reply-To: <201110061854.52856.pedro@codesourcery.com>
> This is a bit a step backwards in that it doesn't allow
> marking parts of the value as unavailable when the type
> is longer than one register. get_frame_register_value
> was invented to allow for partially available registers.
I understand.
The bummer part is that I'm entering my busiest time of the year,
and I haven't followed all this close enough to whip up a quick fix.
So I'll keep that on my list to look at. Note that AVR will
have to remain completely broken. We'll just have to add a note
if we release 7.4 with that problem.
--
Joel
next prev parent reply other threads:[~2011-10-06 20:11 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-03 21:03 Joel Brobecker
2011-10-06 17:55 ` Pedro Alves
2011-10-06 20:11 ` Joel Brobecker [this message]
2011-10-06 21:00 ` Pedro Alves
2011-10-07 16:38 ` Joel Brobecker
2011-10-07 16:52 ` Pedro Alves
2011-10-22 14:48 ` Joel Brobecker
2011-10-25 19:34 ` Pedro Alves
2011-10-25 20:37 ` Joel Brobecker
2011-10-25 21:09 ` Pedro Alves
2011-10-26 21:44 ` Joel Brobecker
2011-10-26 22:11 ` Joel Brobecker
2011-10-27 15:57 ` Tom Tromey
2011-10-27 17:51 ` Joel Brobecker
2011-10-27 2:56 ` Joel Brobecker
2011-10-27 11:10 ` Pedro Alves
2011-10-27 17:56 ` Joel Brobecker
2011-10-31 3:17 ` [RFA] read_frame_register_value and big endian arches Joel Brobecker
2011-11-07 19:42 ` Pedro Alves
2011-11-07 21:24 ` Joel Brobecker
2011-11-10 17:15 ` Checked in: " Joel Brobecker
2011-11-16 18:23 ` Ulrich Weigand
2011-11-18 2:01 ` Joel Brobecker
2011-11-18 17:40 ` Ulrich Weigand
2011-11-18 19:41 ` Joel Brobecker
2011-11-18 20:06 ` [commit] " Ulrich Weigand
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=20111006201053.GS19246@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=pedro@codesourcery.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