Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: Michael Elizabeth Chastain <mec@shout.net>
Cc: fnasser@redhat.com, gdb-patches@sources.redhat.com
Subject: Re: [rfa] new test, pr-1090.exp, multi-register variables
Date: Mon, 24 Feb 2003 04:17:00 -0000	[thread overview]
Message-ID: <20030224041749.GB20002@nevyn.them.org> (raw)
In-Reply-To: <200302240355.h1O3ti606453@duracef.shout.net>

On Sun, Feb 23, 2003 at 09:55:44PM -0600, Michael Elizabeth Chastain wrote:
> This is a new test script for pr gdb/1090, which is about register
> variables which occupy several registers.  Both gdb 5.3 and gdb
> HEAD%20030223 get this wrong.  In my testbed, this happens with
> gcc 2.95.3; gcc v3 compilers don't allocate multi-register variables.
> 
> The symptom of this bug is that gdb prints the first word of a
> structure correctly but botches the second word.  The test has a nice
> KFAIL for this.
> 
> Okay to commit?

You may want to see gdb/214.  Mark posted a proposal for solving it to
gdb@ some weeks ago and it never went further; I don't remember what
the verdict was.

Some day very soon we'll have GDB support to describe this explicitly;
some day after that GCC will output the appropriate debug info
(DW_OP_piece).  May be a little while.

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer


  reply	other threads:[~2003-02-24  4:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-24  3:55 Michael Elizabeth Chastain
2003-02-24  4:17 ` Daniel Jacobowitz [this message]
2003-02-24  7:07   ` Daniel Berlin
2003-02-24  4:35 Michael Elizabeth Chastain
2003-02-24  5:06 ` Daniel Jacobowitz
2003-02-24  7:27 ` Andrew Cagney
2003-02-24 14:21   ` Daniel Jacobowitz
2003-02-24 15:37     ` Andrew Cagney
2003-02-24 15:06 Michael Elizabeth Chastain

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=20030224041749.GB20002@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=fnasser@redhat.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=mec@shout.net \
    /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