From: Hui Zhu <teawater@gmail.com>
To: gdb@sourceware.org
Subject: [RFC] corelow and multi-arch : Move deprecated_add_core_fns to set_gdbarch_regset_from_core_section
Date: Tue, 03 Aug 2010 15:54:00 -0000 [thread overview]
Message-ID: <AANLkTimMdQWsUaeoO09nAEP1KM_ZGp+4R091n+m7DgSb@mail.gmail.com> (raw)
Hi,
I got a some error with multi-arch gdb and a mips core file:
(gdb) core-file ~/tmp/vmcore
warning: "/home/teawater/tmp/vmcore": ambiguous core format, 2 handlers match
warning: wrong size gregset struct in core file
warning: wrong size gregset struct in core file
#0 0x0000000000000000 in ?? ()
(gdb)
This error because sniff_core_bfd return cris_elf_core_fns. So GDB
use cris_elf_core_fns.fetch_core_registers to analyze this mips core.
It return cris_elf_core_fns because core_sniffer of cris_elf_core_fns
and mips-linux-tdep.c:regset_core_fns is default_core_sniffer.
So I think this is not fit with the multi-arch.
Do you think we can begin move deprecated_add_core_fns to
set_gdbarch_regset_from_core_section?
BTW, core_vec->core_read_registers have a argument "which" that
gdbarch_regset_from_core_section doesn't have. Do you think we can
add one to it?
Thanks,
Hui
next reply other threads:[~2010-08-03 15:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-03 15:54 Hui Zhu [this message]
2010-08-03 17:12 ` Ulrich Weigand
2010-08-04 4:55 ` Hui Zhu
2010-08-04 13:53 ` Ulrich Weigand
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=AANLkTimMdQWsUaeoO09nAEP1KM_ZGp+4R091n+m7DgSb@mail.gmail.com \
--to=teawater@gmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).