From: Michael Elizabeth Chastain <mec@shout.net>
To: drow@mvista.com, ezannoni@redhat.com
Cc: gdb-patches@sources.redhat.com
Subject: Re: RFA/dwarf: Fix the GCC 2.95.3 store.exp regression for multi-register variables
Date: Fri, 04 Apr 2003 06:42:00 -0000 [thread overview]
Message-ID: <200304040641.h346fwf16003@duracef.shout.net> (raw)
My test bed says that this is okay. It fixes the regression in
store.exp with gcc 2.95.3 -gdwarf-2 (gcc 2.95.3 is the only compiler
that puts this particular struct into a register). And it doesn't
have any regressions with any gcc v2 or v3, dwarf-2 or stabs+,
on my native i686-pc-linux-gnu.
I have another PR for this, gdb/1107, that comes with a source file
and an executable file. With this patch, gdb HEAD changes from
'new bad behavior' back to 'same bad behavior as 5.3'. Specifically,
I have a structure which is in %ebx and %esi. gdb 5.3 prints values
from %ebx and %esp (the next register in 'info registers').
gdb HEAD prints %ebx and something from god knows where, and
gdb HEAD + patch prints %ebx and %esp again.
(I really hate it when gdb prints the wrong numbers!)
With this patch gdb is better in the store.exp case and not any
worse in the gdb/1107 case. What the heck, here's a table:
store.exp gdb/1107
gdb 5.3 okay wrong
gdb HEAD wrong wrong
gdb HEAD + drow okay wrong
So ... recommended for approval. If it goes in then we can maybe talk
about gdb/1107 some more.
Michael C
===
2003-03-12 Daniel Jacobowitz <drow@mvista.com>
* dwarf2expr.h (struct dwarf_expr_context): Remove extra arguments
to read_reg and update its comment. Remove regnum member.
* dwarf2expr.c (execute_stack_op): Remove memaddr and expr_lval.
Don't call read_reg when setting in_reg. Call read_reg to get
the frame base if it's in a register. Return the register number
on the stack instead of in the context. Remove extra arguments
to read_reg.
* dwarf2loc.c (dwarf_expr_read_reg): Remove extra arguments.
(dwarf2_evaluate_loc_desc): Call value_from_register. Expect
the register number on the expression stack.
(needs_frame_read_reg): Remove extra arguments.
next reply other threads:[~2003-04-04 6:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-04 6:42 Michael Elizabeth Chastain [this message]
2003-04-10 18:01 ` Elena Zannoni
2003-04-13 15:54 ` Daniel Jacobowitz
-- strict thread matches above, loose matches on Subject: below --
2003-03-12 20:41 Daniel Jacobowitz
2003-03-13 21:39 ` Stephane Carrez
2003-04-03 21:52 ` Elena Zannoni
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=200304040641.h346fwf16003@duracef.shout.net \
--to=mec@shout.net \
--cc=drow@mvista.com \
--cc=ezannoni@redhat.com \
--cc=gdb-patches@sources.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