From: "Mark Kettenis" <mark.kettenis@xs4all.nl>
To: "Nick Hudson" <skrll@netbsd.org>
Cc: "Daniel Jacobowitz" <drow@false.org>, gdb-patches@sources.redhat.com
Subject: Re: PATCH: Provde a pid to filename conversion for NetBSD
Date: Sat, 16 Dec 2006 11:18:00 -0000 [thread overview]
Message-ID: <10247.82.92.89.47.1166267903.squirrel@webmail.xs4all.nl> (raw)
In-Reply-To: <200612160846.31929.skrll@netbsd.org>
> On Friday 15 December 2006 16:37, Daniel Jacobowitz wrote:
> > On Fri, Dec 15, 2006 at 04:23:30PM +0000, Nick Hudson wrote:
> > > > 2006-11-30 Nick Hudson <skrll@netbsd.org>
> > > >
> > > > * i386nbsd-nat.c: Include "nbsd-nat.h".
> > > > (_initialize_i386nbsd_nat): Update target vector to use
> > > > nbsd_pid_to_exec_file.
> > > >
> > > > * config/i386/nbsdelf.mh (NATDEPFILES): Add nbsd-nat.o
> > > >
> > > > * nbsd-nat.c: New file.
> > > > * nbsd-nat.h: New file.
> > > > * Makefile.in (ALLDEPFILES): Add nbsd-nat.c.
> > > > (nbsd_nat_h): New variable.
> > > > (nbsd-nat.o): New dependency.
> > >
> > > What needs to happen for this to go in?
> >
> > Someone needs to review it. I was hoping that someone who actually
> > used NetBSD would speak up :-) If no one does, I'll do it myself.
>
> I sent Jason Thorpe (current NetBSD maintainer) an email, but got not
> response. :(
Reasoning that NetBSD and OpenBSD are similar enough, I suppose I can do
it. You're origional diff broke OpenBSD/i386 support, since it re-used
the NetBSD/i386 native code, but I've solved that by moving some code
from i386nbsd-nat.c to i386obsd-nat.c. If I ever get to implement this
for OpenBSD it will not use /proc, and I had some other reasons to make
the seperation anyway. Anyway, your diff looks pretty good, except for
some minor nits:
* Always include "defs.h" first.
* The FSF lawyers have apparently changed their mind again, and we should
use Copyright (C) again.
* Make sure the dependencies in Makefile.in are up to date; you forgot to
add a dependency rule for nbsd-nat.o.
I'll fix those when I commit the diff.
However, before I can do that, I need to be sure you've got an FSF
copyright assignment for GDB in place. Or Daniel, do you think there
is not enough origional code here to warrant one?
> > It looks generally fine. Is this going to work for every NetBSD
> > platform? Should it be added to all of them, rather than just i386?
> > Looks like GDB supports 11.
>
> I have diffs to add support to all other NetBSD platforms which I
> committed to
> the NetBSD tree recently. I'll send those after this one goes in.
Ah, that'd be good. Perhaps that means that a few more NetBSD/OpenBSD
seperation diffs are needed, but that's not a big problem.
> Thanks,
> Nick
next prev parent reply other threads:[~2006-12-16 11:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-30 13:23 Nick Hudson
2006-12-15 16:23 ` Nick Hudson
2006-12-15 16:37 ` Daniel Jacobowitz
2006-12-16 8:46 ` Nick Hudson
2006-12-16 11:18 ` Mark Kettenis [this message]
2006-12-16 17:03 ` Daniel Jacobowitz
2006-12-17 14:32 ` 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=10247.82.92.89.47.1166267903.squirrel@webmail.xs4all.nl \
--to=mark.kettenis@xs4all.nl \
--cc=drow@false.org \
--cc=gdb-patches@sources.redhat.com \
--cc=skrll@netbsd.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