kern/96981: reproducible instant reboot by unprivileged user
Gavin Atkinson
gavin.atkinson at ury.york.ac.uk
Thu May 10 16:20:13 UTC 2007
The following reply was made to PR amd64/96981; it has been noted by GNATS.
From: Gavin Atkinson <gavin.atkinson at ury.york.ac.uk>
To: Lodewijk =?ISO-8859-1?Q?V=F6ge?= <lvoege at gmail.com>
Cc: bug-followup at FreeBSD.org
Subject: Re: kern/96981: reproducible instant reboot by unprivileged user
Date: Thu, 10 May 2007 17:17:49 +0100
I have been able to recreate this on an amd64 system of my own as
follows:
Fresh install of 6.2-RELEASE-amd64
ports tree from 2007.02.13.06.40.00 (newer trees have the port BROKEN on
amd64, for unrelated reasons)
cd /usr/ports/lang/mono && make install
(accept default options for all ports)
As regular user:
Create example file in PR written to 96981.m
$ mcs 96981.m
$ gdb /usr/local/bin/mono
(gdb) set args 96981.exe
(gdb) r
Starting program: /usr/local/bin/mono 96981.exe
(no debugging symbols found)...(no debugging symbols found)...(no
debugging symbols found)...(no debugging symbols found)...(no debugging
symbols found)...(no debugging symbols found)...(no debugging symbols
found)...warning: Unable to get location for thread creation breakpoint:
generic error
[New LWP 100094]
(no debugging symbols found)...(no debugging symbols found)...[New
Thread 0x6eb000 (LWP 100094)]
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x6eb000 (LWP 100094)]
0x00000000004cec66 in GC_push_all_stack ()
(gdb) c
Continuing.
Read from remote host ga9test3.york.ac.uk: Connection reset by peer
Sadly, I don't currently have an amd64 system with a serial port
available.
More information about the freebsd-amd64
mailing list