From: Christopher Faylor <cgf@redhat.com>
To: gdb@sources.redhat.com
Subject: SEGV on display /i $pc with i386 target
Date: Wed, 28 Aug 2002 22:51:00 -0000 [thread overview]
Message-ID: <20020829055103.GA26149@redhat.com> (raw)
I just noticed a SEGV whenever I do a 'display /i $pc' on cygwin.
I tried building a gdb for linux to see what was going wrong on
cygwin but it isn't much better:
(top-gdb) display /i $pc
1: x/i $(null) 0x8072f42 <main+6>: push $0x6
The problem comes from the fact that, while gdb understands that
$pc == $eip, it doesn't seem to know how to rename $pc to $eip
when it is outputting the register name. You can get the same
behavior by doing something like 'display /i $ps', too (even
if that doesn't make sense it shouldn't SEGV).
The simplest way to fix this is to extend the i386_register_names array
to include builtin register names, however, maybe the right way to fix
this is to add something to builtin-reg.c.
I noticed that i386_register_names seems to have 41 elements while
the sum of NUM_REGS + NUM_PSEUDO_REGS == 40. Is that intentional?
cgf
next reply other threads:[~2002-08-29 5:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-28 22:51 Christopher Faylor [this message]
2002-08-29 15:40 ` Mark Kettenis
2002-08-29 18:05 ` Christopher Faylor
2002-08-29 20:37 ` Elena Zannoni
2002-08-29 20:53 ` Christopher Faylor
2002-09-02 13:26 ` Andrew Cagney
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=20020829055103.GA26149@redhat.com \
--to=cgf@redhat.com \
--cc=gdb@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