Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 28 Jan 2001 23:40:57 +0200 (EET)
From:      Maxim Sobolev <sobomax@freebsd.org>
To:        current@freebsd.org
Cc:        phk@freebsd.org
Subject:   Segfaults and dmesg
Message-ID:  <200101282140.f0SLeva12734@vic.sabbo.net>

next in thread | raw e-mail | index | archive | help
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




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200101282140.f0SLeva12734>