From: "Eli Zaretskii" <eliz@gnu.org>
To: Michael Chastain <mec.gnu@mindspring.com>
Cc: kettenis@chello.nl, gdb-patches@sources.redhat.com
Subject: Re: [PATCH] Partial fix for PR backtrace/1718
Date: Sat, 31 Jul 2004 18:44:00 -0000 [thread overview]
Message-ID: <7821-Sat31Jul2004214202+0300-eliz@gnu.org> (raw)
In-Reply-To: <410BB62F.nailFX111607H@mindspring.com> (message from Michael Chastain on Sat, 31 Jul 2004 11:09:35 -0400)
> Date: Sat, 31 Jul 2004 11:09:35 -0400
> From: Michael Chastain <mec.gnu@mindspring.com>
>
> Opcodes 0xb8 to 0xba are for "move immediate", which moves a constant
> immediate value into a register. Opcodes 0xa1 and 0x8b are for "move
> register/memory".
>
> These are different instructions. In C terms,
>
> eax = 0x375aa0; /* move immediate, opcode 0xb8 + rd */
> ebx = 0x375aa0; /* move immediate, opcode 0xb8 + rd */
> eax = * (int *) 0x375aa0; /* move r/m, opcode 0xa1 */
> ebx = * (int *) 0x375aa0; /* move r/m, opcode 0x8b + /r */
Right.
Perhaps, then, you could post a list of all the opcodes and subsequent
bytes that we need to cover in i386_analyze_frame_setup?
next prev parent reply other threads:[~2004-07-31 18:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-24 12:59 Mark Kettenis
2004-07-24 17:58 ` Eli Zaretskii
2004-07-30 18:35 ` Eli Zaretskii
2004-07-30 20:08 ` Mark Kettenis
2004-07-31 13:41 ` Eli Zaretskii
2004-07-31 15:09 ` Michael Chastain
2004-07-31 18:44 ` Eli Zaretskii [this message]
2004-08-01 5:35 ` Michael Chastain
2004-08-01 13:54 Mark Kettenis
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=7821-Sat31Jul2004214202+0300-eliz@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=kettenis@chello.nl \
--cc=mec.gnu@mindspring.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