From: Orjan Friberg <orjan.friberg@axis.com>
To: gdb-patches@sources.redhat.com,
Hans-Peter Nilsson <hans-peter.nilsson@axis.com>
Subject: [CRIS] Reading core file selects "wrong" mach
Date: Wed, 01 Dec 2004 14:00:00 -0000 [thread overview]
Message-ID: <41ADCE5B.5010001@axis.com> (raw)
When reading a CRISv32 Linux core file, the "wrong" mach is selected, causing
cris_elf_grok_prstatus to not find the general-purpose registers (because unlike
other ports it actually checks bfd_get_mach (abfd)).
The reason seems to be the call to bfd_default_set_arch_mach (abfd, ebd->arch,
0) in elf_core_file_p in elfcore.h which will select the default mach for that
arch. Directly after this we start reading the core file which results in a
call to cris_elf_grok_prstatus (which fails because the default mach doesn't
match the current mach).
Is there an implicit assumption that the mach is not to be trusted when reading
a core file?
(For reference: e_flags, checked in set_mach_from_flags, is hardcoded to 0 in
the Linux kernel, but setting it correctly (to EF_CRIS_VARIANT_V32 in this case)
wouldn't change a thing because of the above.)
--
Orjan Friberg
Axis Communications
next reply other threads:[~2004-12-01 14:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-01 14:00 Orjan Friberg [this message]
2004-12-01 16:14 ` Randolph Chung
2004-12-02 10:15 ` Orjan Friberg
2004-12-02 15:42 ` Randolph Chung
2004-12-02 17:18 ` Mark Kettenis
2004-12-13 15:12 ` Orjan Friberg
2004-12-13 16:09 ` Hans-Peter Nilsson
2004-12-13 20:22 ` Mark Kettenis
2005-01-14 17:10 ` Orjan Friberg
2005-01-14 18:40 ` Hans-Peter Nilsson
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=41ADCE5B.5010001@axis.com \
--to=orjan.friberg@axis.com \
--cc=gdb-patches@sources.redhat.com \
--cc=hans-peter.nilsson@axis.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