From: Andreas Schwab <schwab@suse.de>
To: root@chaos.analogic.com
Cc: Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: modutils-2.3.15 'insmod'
Date: Wed, 09 Jul 2003 17:45:22 +0200 [thread overview]
Message-ID: <jer84zln59.fsf@sykes.suse.de> (raw)
In-Reply-To: <Pine.LNX.4.53.0307091119450.470@chaos> (Richard B. Johnson's message of "Wed, 9 Jul 2003 11:25:11 -0400 (EDT)")
"Richard B. Johnson" <root@chaos.analogic.com> writes:
|> It is likely that malloc(0) returning a valid pointer is a bug
|> that has prevented this problem from being observed.
It's not a bug, it's a behaviour explicitly allowed by the C standard.
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux AG, Deutschherrnstr. 15-19, D-90429 Nürnberg
Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2003-07-09 15:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-09 15:25 modutils-2.3.15 'insmod' Richard B. Johnson
2003-07-09 15:45 ` Andreas Schwab [this message]
2003-07-09 16:04 ` Bill Rugolsky Jr.
2003-07-09 22:44 ` H. Peter Anvin
2003-07-09 23:51 ` Richard B. Johnson
2003-07-09 16:08 ` Kurt Wall
2003-07-09 16:33 ` Andy Isaacson
2003-07-14 11:41 ` Keith Owens
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=jer84zln59.fsf@sykes.suse.de \
--to=schwab@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=root@chaos.analogic.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