[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Bug-gforth] Crash on OS X

From: Bernd Paysan
Subject: Re: [Bug-gforth] Crash on OS X
Date: Fri, 2 Apr 2010 21:34:01 +0200
User-agent: KMail/1.13.2 (Linux/; KDE/4.4.2; x86_64; ; )

Am Sonntag 21 Februar 2010 21:44:53 schrieb Bernd Paysan:
> Am Sonntag 21 Februar 2010 21:22:16 schrieb Torbjorn Kristoffersen:
> > I typed "see drop" in Gforth 0.7.0 on Mac OS X Snow Leopard (10.6.2 on
> > a Mac Pro) and the OS started behaving completely erratically.
> > 
> > For one, all the icons on my desktop disappeared and I could no longer
> > start any programs.
> > I had a shell open, and it told me my user was suddenly gone.  "id"
> > revealed that I had a uid, but no username!
> > Upon a restart, everything was fine again. I've reproduced the bug 3
> > times by typing "see drop".
> > 
> > Did Gforth trigger a nasty OS X bug?  Can anyone else please confirm
> > this?
> I tried this and it seems to work fine (from within Gforth, the
> disassembler output was as expected), but then all hell break lose.  I
> couldn't start the Finder any more, the software update that found
> something didn't react, and finally, the menu folded down (Mac OS X 10.5).
>  I can confirm that this triggers a nasty Mac OS X bug.
> What we do for see <primitive> on x86_64 is: We start gdb, and advice it to
> produce an assembler dump of the region of the primitive.

This seems now be fixed with the most recent Mac OS X bug - it now again works 
for me.  We had a bug report earlier here (one year ago), where I couldn't 
reproduce it.


I strongly suspect that this bug was introduced into Mac OS X about one year 
ago, and my usual update lag back then caused me to mark the problem as "works 
for me" back then.

Bernd Paysan
"If you want it done right, you have to do it yourself"

Attachment: signature.asc
Description: This is a digitally signed message part.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]