Hank Roberts wrote:
> I've installed Fink three times now, just to get the "jstar" WordStar clone
> working so I can type properly.  Each time -- and this may just be

What's this jstar thing? Not a fink package, surely.

> coincidence -- within a day I get crashes in all sorts of applications, all

There are buggy applications out there, but if you want help, you need 
to name them. The great majority of applications is stable and does not 
do this.

> starting with the lines:
> Exception:  EXC_BAD_ACCESS (0x0001)
> Codes:      KERN_INVALID_ADDRESS (0x0001)

Yes, this is part of one of the generic messages that you get from a 
crashing application. It does not say anything about the reason for the 
crash.
> 
> and each time, finally, I've had to reformat the drive and reinstall.

"Had to"? I am sure you are overreacting. I have *never ever* 
reformatted a drive and reinstalled, and I am constantly doing dangerous 
and often foolish things with OSX and Fink. I only once had to reinstall 
fink after having erased it accidentally (Trying to free some space on a 
firewire disk, I deleted the 1.4GB fink directory I found there. Turned 
out it had been a symlink to /sw :-()

> Now I don't blame Fink -- this definitely happens even when I haven't
> installed Fink, within a couple of weeks' use of OS X.  I find the error
> message is from Mach code via BSD Unix, a virtual memory problem.  Nobody
> in Apple's "Amateur Hour" discussion boards answers questions about it, I
> would guess it's a known bug on some internal list that we mere users don't
> see.

No, it is not "a bug", so nobody can give any meaningful answer unless 
you provide more specific details.

> But, stop me before I try again, if anyone around here knows for sure
> whether or not OS X 10.1.5 itself is stable enough to be messing with Fink.

As Justin said, both OSX and Fink are as stable as OSes come. Nothing to 
worry about, in general. But applications do crash, on any OS. In my own 
folder ~/Library/Logs, where the crash reports are stored (an extremely 
useful feature of OSX, BTW, not to be found by default on most other 
OSes), I am seeing accumulated crash logs for 37 applications, ranging from
AbiWord_d.crash.log and Acrobat Reader 5.0.crash.log over
Terminal.crash.log  and XDarwin.crash.log to
xfce.crash.log, xfig.crash.log and xmgrace.crash.log

Most of them are either one-time crashes or crashes from experimental 
versions of programs that are being or have been debugged in the 
meantime. The crash logs can be very useful for this debugging phase.

-- 
Martin




-------------------------------------------------------
This sf.net email is sponsored by: Dice - The leading online job board
for high-tech professionals. Search and apply for tech jobs today!
http://seeker.dice.com/seeker.epl?rel_code=31
_______________________________________________
Fink-beginners mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/fink-beginners

Reply via email to