From: "David O'Brien" <obrien@freebsd.org>
To: Mark Kettenis <kettenis@chello.nl>
Cc: gdb@sources.redhat.com, dan@debian.org, amitkale@emsyssoft.com,
peter@freebsd.org, fvdl@netbsd.org
Subject: Re: [RFC] Adding %cs and %ss for AMD64 to GDB
Date: Fri, 02 Jan 2004 01:25:00 -0000 [thread overview]
Message-ID: <20040102011937.GA79393@dragon.nuxi.com> (raw)
In-Reply-To: <200401010051.i010p5Yg016798@elgar.kettenis.dyndns.org>
On Thu, Jan 01, 2004 at 01:51:05AM +0100, Mark Kettenis wrote:
> * FreeBSD kgdb supplies %cs and %ss in the slots that are now reserved
> for %ds and %es. It provides zero for %fs and %gs (which it thinks
> are %ds and %es). The impact would be positive!
From a FreeBSD POV, I would like to see the change made. We can easily
handle the change.
--
-- David (obrien@FreeBSD.org)
prev parent reply other threads:[~2004-01-02 1:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-01 0:51 Mark Kettenis
2004-01-01 6:15 ` Amit S. Kale
2004-01-01 7:47 ` Daniel Jacobowitz
2004-01-02 1:25 ` David O'Brien [this message]
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=20040102011937.GA79393@dragon.nuxi.com \
--to=obrien@freebsd.org \
--cc=amitkale@emsyssoft.com \
--cc=dan@debian.org \
--cc=fvdl@netbsd.org \
--cc=gdb@sources.redhat.com \
--cc=kettenis@chello.nl \
--cc=peter@freebsd.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