From: Daniel Jacobowitz <drow@mvista.com>
To: Andrew Cagney <ac131313@ges.redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [rfc] 16 bit real-mode for the i386
Date: Thu, 29 Aug 2002 14:37:00 -0000 [thread overview]
Message-ID: <20020829213653.GA24048@nevyn.them.org> (raw)
In-Reply-To: <3D6E8453.5080306@ges.redhat.com>
On Thu, Aug 29, 2002 at 04:30:11PM -0400, Andrew Cagney wrote:
> Hello,
>
> The attached modifies i386-tdep.c so that there is a ``set i386
> real-mode'' command (doco to go).
>
> When real-mode is enabled, GDB computes the ``20 bit'' ``stop address''
> (aka PC but not to be confused with $pc ... :-) from both the $cs and
> $pc registers. That way, core GDB sees a cannonical PC address that
> (regardless of $cs) will match a ``20 bit'' breakpoint address.
>
> Thoughts?
>
> I'm desperatly trying to come up with a test-case mind. This is a
> rewrite of an old old patch (that hacked breakpoint.c) and the original
> testcase has been lost :-(
>
> Andrew
Now, my i386 knowledge is a bit rusty. But:
> +static CORE_ADDR
> +i386_read_pc (ptid_t ptid)
> +{
> + CORE_ADDR pc = read_register_pid (PC_REGNUM, ptid);
> + if (i386_real_mode_p)
> + {
> + CORE_ADDR cs = read_register_pid (CS_REGNUM, ptid);
> + pc = pc + (cs << 4);
> + }
> + return pc;
> +}
> +
> +static void
> +i386_write_pc (CORE_ADDR pc, ptid_t ptid)
> +{
> + if (i386_real_mode_p)
> + {
> + CORE_ADDR cs = read_register_pid (CS_REGNUM, ptid);
> + pc = pc - (cs << 4);
> + }
> + write_register_pid (PC_REGNUM, pc, ptid);
> +}
> +
Left shift of _four_? Surely the PC is more than four bits.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2002-08-29 21:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-29 13:33 Andrew Cagney
2002-08-29 14:37 ` Daniel Jacobowitz [this message]
2002-08-29 14:46 ` Kevin Buettner
2002-08-29 14:52 ` Daniel Jacobowitz
2002-08-29 14:46 ` Andrew Cagney
2002-08-30 12:31 ` Eli Zaretskii
2002-08-29 15:36 ` Mark Kettenis
2002-08-30 12:47 ` 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=20020829213653.GA24048@nevyn.them.org \
--to=drow@mvista.com \
--cc=ac131313@ges.redhat.com \
--cc=gdb-patches@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