From: Joel Brobecker <brobecker@adacore.com>
To: Doug Evans <dje@google.com>
Cc: gdb <gdb@sourceware.org>
Subject: Re: store.exp failure on i686-linux with newer gcc's
Date: Thu, 03 Sep 2009 21:58:00 -0000 [thread overview]
Message-ID: <20090903215811.GI4379@adacore.com> (raw)
In-Reply-To: <e394668d0909031450te808c15h87a2f884b38a7281@mail.gmail.com>
> value->lval is set to not_lval and value_assign doesn't like that so
> gdb refuses to set the variable with "Left operand of assignment is
> not an lvalue."
IIRC, this is a know limitation in GDB. Daniel wrote the piece that
allows us to read variables that are spread across several locations
like this. But i don't think anyone has thought about being able
to write to such a variable.
--
Joel
next prev parent reply other threads:[~2009-09-03 21:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-03 21:50 Doug Evans
2009-09-03 21:58 ` Joel Brobecker [this message]
2009-09-03 22:04 ` Pedro Alves
2009-09-03 22:17 ` Doug Evans
2009-09-03 23:44 ` Nathan Froyd
2009-09-04 16:05 ` Tom Tromey
2009-09-04 17:49 ` Nathan Froyd
2009-09-04 18:38 ` Tom Tromey
2009-09-04 20:17 ` Nathan Froyd
2009-09-04 20:18 ` Doug Evans
2009-09-04 21:23 ` Tom Tromey
2009-09-04 21:28 ` Daniel Jacobowitz
2009-09-04 22:28 ` Tom Tromey
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=20090903215811.GI4379@adacore.com \
--to=brobecker@adacore.com \
--cc=dje@google.com \
--cc=gdb@sourceware.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