From owner-freebsd-current  Sun Jan 28 13:41:20 2001
Delivered-To: freebsd-current@freebsd.org
Received: from blizzard.sabbo.net (ns.sabbo.net [193.193.218.18])
	by hub.freebsd.org (Postfix) with ESMTP
	id F048B37B402; Sun, 28 Jan 2001 13:40:56 -0800 (PST)
Received: from vic.sabbo.net (root@vic.sabbo.net [193.193.218.112])
	by blizzard.sabbo.net (8.10.1/8.10.1) with ESMTP id f0SLerT32303;
	Sun, 28 Jan 2001 23:40:54 +0200
Received: (from max@localhost)
	by vic.sabbo.net (8.11.1/8.9.3) id f0SLeva12734;
	Sun, 28 Jan 2001 23:40:57 +0200 (EET)
	(envelope-from sobomax@FreeBSD.org)
From: Maxim Sobolev <sobomax@freebsd.org>
Message-Id: <200101282140.f0SLeva12734@vic.sabbo.net>
Subject: Segfaults and dmesg
To: current@freebsd.org
Date: Sun, 28 Jan 2001 23:40:57 +0200 (EET)
Cc: phk@freebsd.org
X-Mailer: ELM [version 2.5 PL3]
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Hi,

I wonder if anyone noticed that segfault messages are no longer appended
to the dmesg output. For me it looks like serious POLA violation. The
following script highlights the problem:

--- kaboom.sh ---
#!/bin/sh
dmesg -a > dmesg.old
cat > tst.c << EOF
#include <stdio.h>
main () { return strlen((char *)NULL); }
EOF
cc tst.c -o tst
./tst
dmesg -a > dmesg.new
diff -d dmesg.old dmesg.new
rm -f dmesg.old tst.c tst dmesg.new
------------------

On a 4-STABLE system:
max@vic$ ./kaboom.sh
./kaboom.sh: line 7: 12717 Segmentation fault      ./tst
345a345
> pid 12717 (tst), uid 1001: exited on signal 11
max@vic$

Whereas on a 5-CURRENT:
max@notebook$ ./kaboom.sh
./kaboom.sh: line 7:   333 Segmentation fault      ./tst
max@notebook$

Please fix.

-Maxim


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message