Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Doug Evans <dje@google.com>
To: gdb <gdb@sourceware.org>
Subject: store.exp failure on i686-linux with newer gcc's
Date: Thu, 03 Sep 2009 21:50:00 -0000	[thread overview]
Message-ID: <e394668d0909031450te808c15h87a2f884b38a7281@mail.gmail.com> (raw)

Hi.

Anyone working on this failure?

FAIL: gdb.base/store.exp: var longest l; print new l, expecting -1
[should read "expecting 4", fixed in separate patch]
FAIL: gdb.base/store.exp: var longest l; print incremented l, expecting 2
FAIL: gdb.base/store.exp: upvar longest l; print new l, expecting 4
FAIL: gdb.base/store.exp: var struct 4 u; print new u, expecting {s =
\{1, 2, 3, 4}}
FAIL: gdb.base/store.exp: up struct 4 u; print new u, expecting {s =
\{1, 2, 3, 4}}

Newer gcc's can store a 64 bit int in non-contiguous registers and use
DW_OP_piece to mark each piece.

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."

It seems like we need to not mark the value as not_lval and teach the
relevant pieces how to handle such values.
Anyone thought about how they want this done?


             reply	other threads:[~2009-09-03 21:50 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-03 21:50 Doug Evans [this message]
2009-09-03 21:58 ` Joel Brobecker
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=e394668d0909031450te808c15h87a2f884b38a7281@mail.gmail.com \
    --to=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