Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Robert Millan <rmh@debian.org>
To: Mark Kettenis <kettenis@chello.nl>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] i386bsd-nat.c tweak
Date: Thu, 12 Aug 2004 09:39:00 -0000	[thread overview]
Message-ID: <20040812093906.GA36673@khazad.dyndns.org> (raw)
In-Reply-To: <200408120855.i7C8tN57065199@elgar.kettenis.dyndns.org>

On Thu, Aug 12, 2004 at 10:55:23AM +0200, Mark Kettenis wrote:
> 
>    This disables the code below on GNU/kFreeBSD, but it's still enabled in
>    FreeBSD 4.x or later.
> 
> Yes indeed.
> 
> [...]
> 
>    Build on GNU/kFreeBSD still works, but it might be that keeping
>    SC_REG_OFFSET undefined results in a weird runtime bug that will be
>    difficult to trace, so I'd really like to be sure this part is ok.
> 
> It will be caught on normal FreeBSD.

We have this check:

  #if defined (__FreeBSD_version) && __FreeBSD_version >= 400011
  #define SC_REG_OFFSET i386fbsd4_sc_reg_offset

This ensures that SC_REG_OFFSET is defined for either 4.x or 5.x (i.e. any
non-obsolete version of FreeBSD).  If not defining it triggers a bug, how
can it be caught on normal FreeBSD, if that situation never happens?

Perhaps what you want is something like this?:

  #if defined (__FreeBSD_version) && __FreeBSD_version >= 400011 \
  	__FreeBSD_version < 500000
  #define SC_REG_OFFSET i386fbsd4_sc_reg_offset

Then i386fbsd4_sc_reg_offset would be for 4.x only, which seems like the
intended result.  Is that it?

-- 
Robert Millan

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


      reply	other threads:[~2004-08-12  9:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-09 20:48 Mark Kettenis
2004-08-09 22:44 ` Robert Millan
2004-08-12  8:55   ` Mark Kettenis
2004-08-12  9:39     ` Robert Millan [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=20040812093906.GA36673@khazad.dyndns.org \
    --to=rmh@debian.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=kettenis@chello.nl \
    /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