git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Glanzmann <thomas@glanzmann.de>
To: Thomas Schwinge <tschwinge@gnu.org>
Cc: git@vger.kernel.org,
	Michael Gernoth <simigern@cip.informatik.uni-erlangen.de>
Subject: Re: [PATCH] Don't rely on unspecified behavior
Date: Sat, 28 Jul 2007 19:39:48 +0200	[thread overview]
Message-ID: <20070728173948.GD23337@cip.informatik.uni-erlangen.de> (raw)
In-Reply-To: <11856407791617-git-send-email-tschwinge@gnu.org>

Hello,

> Calling access(p, m) with p == NULL is not specified, so don't do
> that.  On GNU/Hurd systems doing so will result in an SIGSEGV.

a friend of mine choked on this one when tried git for the second time
(the first time "git-repack -a -d -f" screwed his repository after the
initial checkout. This is fixed for a long time). Lucky me that he had
his libusbdriver in LD_PRELOAD which could not handle the NULL argument.
And I always thought libc would make the check before it does the system
call or does GNU/hurts not use the gnu libc?

	Thomas

  reply	other threads:[~2007-07-28 17:39 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-28 16:39 [PATCH] Support building on GNU/Hurd Thomas Schwinge
2007-07-28 16:39 ` [PATCH] Don't rely on unspecified behavior Thomas Schwinge
2007-07-28 17:39   ` Thomas Glanzmann [this message]
2007-07-28 18:25     ` Thomas Schwinge
2007-07-28 18:26     ` Thomas Schwinge
2007-07-28 19:30       ` Johannes Schindelin
2007-07-28 19:34         ` Thomas Glanzmann
2007-07-28 20:16           ` Johannes Schindelin
2007-07-28 20:20             ` Thomas Glanzmann
2007-07-28 19:43         ` Thomas Schwinge
2007-07-28 20:17           ` Johannes Schindelin

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=20070728173948.GD23337@cip.informatik.uni-erlangen.de \
    --to=thomas@glanzmann.de \
    --cc=git@vger.kernel.org \
    --cc=simigern@cip.informatik.uni-erlangen.de \
    --cc=tschwinge@gnu.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;
as well as URLs for NNTP newsgroup(s).