From: Michal Ludvig <mludvig@suse.cz>
To: gdb@sources.redhat.com
Cc: Andrew Cagney <ac131313@redhat.com>,
Michael Elizabeth Chastain <mec@shout.net>,
Mark Kettenis <kettenis@chello.nl>
Subject: regcache (Re: GDB respin)
Date: Thu, 06 Feb 2003 14:30:00 -0000 [thread overview]
Message-ID: <3E427169.5010702@suse.cz> (raw)
In-Reply-To: <3E3EA35D.3080300@redhat.com>
Andrew Cagney wrote:
> Can someone post backtraces?
>
> 49 gdb.log:../../gdb-head/gdb/sentinel-frame.c:102:
> internal-error: Function sentinal_frame_pop called
>
> Er, this should shouldn't happen. Backtrace?
>
> 3 gdb.log:../../gdb-head/gdb/regcache.c:713: internal-error:
> regcache_raw_read: Assertion `regcache != NULL && buf != NULL' failed.
>
> Again, the caller is pretty messed up.
>
> 5 gdb.log:../../gdb-head/gdb/gdbarch.c:4271: internal-error:
> gdbarch: gdbarch_store_return_value invalid
> 2 gdb.log:&"../../gdb-head/gdb/gdbarch.c:4252: internal-error:
> gdbarch: gdbarch_extract_return_value invalid\n"
> 6 gdb.log:../../gdb-head/gdb/gdbarch.c:4252: internal-error:
> gdbarch: gdbarch_extract_return_value invalid
The problem on x86-64 is probably caused by the regbuf vs. regcache
usage. This is a part of the patch that broke the testsuite:
diff -u -p -r1.33 -r1.34
--- gdb/x86-64-tdep.c 26 Oct 2002 10:37:45 -0000 1.33
+++ gdb/x86-64-tdep.c 26 Oct 2002 16:56:34 -0000 1.34
@@ -925,11 +925,35 @@ x86_64_init_abi (struct gdbarch_info inf
+ set_gdbarch_long_double_bit (gdbarch, 128);
+ set_gdbarch_ps_regnum (gdbarch, 17); /* %eflags */
+ set_gdbarch_stab_reg_to_regnum (gdbarch, x86_64_dwarf2_reg_to_regnum);
+ set_gdbarch_dwarf_reg_to_regnum (gdbarch, x86_64_dwarf2_reg_to_regnum);
+ set_gdbarch_extract_return_value (gdbarch, NULL);
+ set_gdbarch_store_return_value (gdbarch, NULL);
+ set_gdbarch_extract_struct_value_address (gdbarch, NULL);
If I comment out last three lines (those return_value related), the
testsuite performs much better. But all the other lines seem have some
influence on the results.
I'm about to convert x86-64 target to use regcache, but am not sure what
must be done for it. Could someone please briefly explain me what is
regcache all about and what must be changed in order to have the target
regcache-compilant?
As I was looking to the sources I believe, that only
x86_64_store_return_value() and x86_64_extract_return_value() must be
modified. Am I right or not?
Thanks.
Michal Ludvig
--
* SuSE CR, s.r.o * mludvig@suse.cz
* (+420) 296.545.373 * http://www.suse.cz
next prev parent reply other threads:[~2003-02-06 14:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-03 16:15 GDB respin Michael Elizabeth Chastain
2003-02-03 17:14 ` Andrew Cagney
2003-02-03 18:08 ` Elena Zannoni
2003-02-06 14:30 ` Michal Ludvig [this message]
2003-02-06 18:14 ` regcache (Re: GDB respin) Andrew Cagney
2003-02-06 23:24 ` [PATCH] " Mark Kettenis
2003-02-07 15:46 ` Michal Ludvig
2003-02-09 10:20 ` Andrew Cagney
2003-02-10 21:26 ` Michal Ludvig
2003-02-10 22:42 ` Mark Kettenis
2003-02-11 16:31 ` Andrew Cagney
2003-02-11 23:12 ` Michal Ludvig
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=3E427169.5010702@suse.cz \
--to=mludvig@suse.cz \
--cc=ac131313@redhat.com \
--cc=gdb@sources.redhat.com \
--cc=kettenis@chello.nl \
--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