Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Robert Millan <rmh@debian.org>
To: Mark Kettenis <kettenis@chello.nl>,
	Nathanael Nerode <neroden@twcny.rr.com>
Cc: gdb-patches@sources.redhat.com, glibc-bsd-hackers@nongnu.org
Subject: Re: [PATCH] GNU/k*BSD fixes [w/ChangeLog]
Date: Mon, 09 Aug 2004 16:32:00 -0000	[thread overview]
Message-ID: <20040809162831.GD2417@khazad.dyndns.org> (raw)
In-Reply-To: <200408090659.i796xKMs000507@elgar.kettenis.dyndns.org>


[ Nathanael, your email server at rr.com is rejecting my mail due to
blacklisting.  You will probably only read this message through gdb-patches.
I have tried neroden-guest@alioth.debian.org too, with no luck. Please tell
me an address where I can reach you. ]

On Sun, Aug 08, 2004 at 11:59:32PM -0400, Nathanael Nerode wrote:
> +#if defined(__FreeBSD__) && !defined(__FreeBSD_kernel__)
> +# define __FreeBSD_kernel__ __FreeBSD__
> +#endif
> +#ifdef __FreeBSD_kernel__
> +# include <osreldate.h>
> +# ifndef __FreeBSD_kernel_version
> +#  define __FreeBSD_kernel_version __FreeBSD_version
> +# endif
> +#endif
> 
> ...and I wondered if it is absolutely guaranteed that <osreldate.h> will
> exist on all FreeBSD and FreeBSD-kernel systems of any possible vintage
> supported by GDB.  Cause otherwise this could break the build on other
> systems.

Asides GNU/kFreeBSD I'm not aware of other non-FreeBSD systems using kernel
of FreeBSD.  Wrt different versions of FreeBSD, I can't be completely sure some
arcane version of FreeBSD didn't have osreldate.h.

I propose the following alternative, which also looks cleaner:

#ifdef HAVE_SYS_PARAM_H
#include <sys/param.h> /* __FreeBSD_{kernel_,}version */
#endif
#if defined(__FreeBSD__) && !defined(__FreeBSD_kernel__)
# define __FreeBSD_kernel__ __FreeBSD__
# define __FreeBSD_kernel_version __FreeBSD_version
#endif

(note: osreldate.h and sys/param.h are equivalent for this purpose)


On Mon, Aug 09, 2004 at 08:59:20AM +0200, Mark Kettenis wrote:
> 
> Yuck, the #ifdef mess in i386bsd-nat.c gets ugly.  I think it should
> be simplified.

Does the proposed alternative above address this concern?

> You're probably changing it to avoid the warning about
> the offsets in `struct sigcontext'.  If I just drop the support for
> ancient BSD (which isn't used anyway) we can avoid that.  You won't
> get the extra check on GNU/kFreeBSD then, but as long as enough people
> use GDB on normal FreeBSD/i386, this doesn't really matter.

The oldest version of kFreeBSD we ever supported is 4.6, so compatibility
with 3.x is not an issue for us.  If you want to drop support for 3.x, that
is fine with me.

> Considering the changes to bsd-kvm.c.  We shouldn't include config.h
> directly.  In GDB "defs.h" does that for us.

Ok.

> I assume that GNU/k*BSD
> still has libkvm.  Why doesn't it have <nlist.h>?  If not, then where
> does it get its `struct nlist' from?

We have libkvm, but not nlist() which is not part of Glibc.  I'm considering
adding nlist() and other functions in a compatibility library (e.g. libbsd),
though.

But I was surprised that disabling the '#include <nlist.h>' didn't cause the
build process to fail on missing declarations.  Does bsd-kvm.c really work
without nlist, or am I missing something?

-- 
Robert Millan

(Debra and Ian) (Gnu's Not (UNiplexed Information and Computing System))/\
(kernel of *(Berkeley Software Distribution))


  reply	other threads:[~2004-08-09 16:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-07  2:20 Robert Millan
2004-08-09  6:59 ` Mark Kettenis
2004-08-09 16:32   ` Robert Millan [this message]
2004-08-09 17:48     ` Mark Kettenis
2004-08-09 19:19       ` Robert Millan
2004-08-09 21:25         ` Mark Kettenis
2004-08-09 22:34           ` Robert Millan
2004-08-09  3:59 Nathanael Nerode

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=20040809162831.GD2417@khazad.dyndns.org \
    --to=rmh@debian.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=glibc-bsd-hackers@nongnu.org \
    --cc=kettenis@chello.nl \
    --cc=neroden@twcny.rr.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