From: Mark Kettenis <kettenis@science.uva.nl>
To: thorpej@wasabisystems.com
Cc: gdb-patches@sourceware.cygnus.com
Subject: Re: [patch] Overhaul i386nbsd-nat.c, add support for XMM + ELF core files
Date: Sat, 05 Jan 2002 06:07:00 -0000 [thread overview]
Message-ID: <200201051406.g05E6tC11463@soliton.wins.uva.nl> (raw)
In-Reply-To: <20020104190350.K9599@dr-evil.shagadelic.org> (message from Jason R Thorpe on Fri, 4 Jan 2002 19:03:50 -0800)
Date: Fri, 4 Jan 2002 19:03:50 -0800
From: Jason R Thorpe <thorpej@wasabisystems.com>
On Sat, Jan 05, 2002 at 01:39:52AM +0100, Mark Kettenis wrote:
> Is there any chance that I can convince you to make NetBSD use
> i386bsd-nat.c instead of i386nbsd-nat.c? NetBSD is close enough to
> FreeBSD and OpenBSD to be able to use the same basic functionality on
> all of them.
[From your first message]
I'd really rather not (the other BSD's don't have the XMM functionality,
for example), but I'll take a look to see if it's really feasible.
My secret agenda of course is that when FreeBSD gets XMM
functionality, GDB will already have the support for it :-).
Likewise, when NetBSD implements support for the debug registers
(which FreeBSD already has), the support will already be there!
Note, i386nbsd-nat.c is still going to be necessary, since NetBSD uses
different core files than the others.
Sure!
[From your second message]
Alright, I did this; it wasn't quite as nasty as I thought it'd be.
Well, I tried hard to write i386bsd.c such that it could be used on
all BSD's :-).
OK to commit?
Yes please!
Thanks,
Mark
prev parent reply other threads:[~2002-01-05 14:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-04 16:08 Jason R Thorpe
2002-01-04 16:41 ` Mark Kettenis
2002-01-04 17:05 ` Jason R Thorpe
2002-01-04 19:03 ` Jason R Thorpe
2002-01-04 19:28 ` Michael Snyder
2002-01-04 19:41 ` Andrew Cagney
2002-01-05 12:59 ` Michael Snyder
2002-01-05 6:07 ` Mark Kettenis [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=200201051406.g05E6tC11463@soliton.wins.uva.nl \
--to=kettenis@science.uva.nl \
--cc=gdb-patches@sourceware.cygnus.com \
--cc=thorpej@wasabisystems.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