Imported from the Apple Support Forums via the Wayback Machine 🔗
Hi folks, I did a search on the web and on this site for this info and couldn't find anything so I'm posting...
I run gnu backgammon using terminal, which launches X11 to run the app. This has been working fine until today, after I updated to 10.6.3. I upgraded first thing this morning and the program ran fine for a few hours. I shut it down and later restarted it and I now get "segmentation fault, process ended"
Can't find anything to help me get this resolved. Can anyone help?
Contact the developer of gnu backgammon or run RAM checkers such as Apple Hardware Test or Rember.
0
Erin U·
Imported from the Apple Support Forums via the Wayback Machine 🔗
I'm having the same problem. At first after the update, it was running fine, but since closing it when I try to open, I now get the error "segmentation fault".
0
CT·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Who is crashing? Terminal? If so, I would at least try trashing the Terminal preferences (~/Library/Preferences/com.apple.Terminal.plist).
And/or try trashing the preferences for each of the involved applications.
charlie
0
Erin U·
Imported from the Apple Support Forums via the Wayback Machine 🔗
It's gnubg that's crashing, it doesn't open at all, but I have crash logs. Terminal and x11 stay open and working.
Do you have gnubg? Is it still working for you after the 10.6.3 update?
0
TomPDX·
Imported from the Apple Support Forums via the Wayback Machine 🔗
I wouldn't necessarily say it is gnu BG that is crashing since it relies on so many other components to run. the fact that is was working fine until the update means it could be any component that is loaded in the chain. Not being a terminal/X11 expert I couldn't say which one but I won't jump to the conclusion that gnubg is the root cause here. someone has posted to the gnubg bug list so both avenues are being pursued.
0
JamesConnolly·
Imported from the Apple Support Forums via the Wayback Machine 🔗
TomPDX and others:
I've just updated to 10.6.3 and have found this segmentation fault.
But it didn't do that immediately:
First, it chugged away taking up 99% of the CPU. I left it overnight thinking it was just rebuilding it's databases like the first time it ran.
Next morning I found no GNUBG. Manual restart from the command line showed segmentation fault.
Any news on this ? I had a quick look at the gnu home page but can't find any discussion there.