From: Mark Kettenis <kettenis@chello.nl>
To: cagney@gnu.org
Cc: thorpej@wasabisystems.com, gdb@sources.redhat.com
Subject: Re: The VAX
Date: Mon, 12 Apr 2004 19:00:00 -0000 [thread overview]
Message-ID: <200404121738.i3CHcfal032199@elgar.kettenis.dyndns.org> (raw)
In-Reply-To: <407AC712.9020702@gnu.org> (message from Andrew Cagney on Mon, 12 Apr 2004 12:42:58 -0400)
Date: Mon, 12 Apr 2004 12:42:58 -0400
From: Andrew Cagney <cagney@gnu.org>
> I've successfully installed NetBSD 1.6.1 on a VAX simulator. The
> performance is actually quite reasonable on my AMD64 box. It is
> currently compiling GDB.
>
> Anyway, I'm working on GDB's VAX target. Hopefully I'll have a
> working native NetBSD/vax configuration soon. I'm already working on
> frameifying vax-tdep.c. So stay tuned, and don't throw away the
> current VAX stuff just yet...
Been there, done that. Per my earlier e-mails, NetBSD/VAX GDB doesn't
build - the nat code is simply missing.
I've got a working NetBSD/vax GDB now. The BSD-specific nat code is
already checked in :-). I just need to tweak the config files, but I
don't want to do that now since that'll probably mean I'll have to
rebuild everything, which is a bit time-consuming. I'll do that when
I'm finished rewriting the code in vax-tdep.c.
In the mean time, would it be a problem if frameifying the VAX would
nuke signal trampoline handling on Ultrix? Not that I expect it to be
working...
Mark
next prev parent reply other threads:[~2004-04-12 17:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-12 16:43 Mark Kettenis
2004-04-12 17:39 ` Andrew Cagney
2004-04-12 19:00 ` Mark Kettenis [this message]
2004-04-12 21:25 ` 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=200404121738.i3CHcfal032199@elgar.kettenis.dyndns.org \
--to=kettenis@chello.nl \
--cc=cagney@gnu.org \
--cc=gdb@sources.redhat.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