XQuartz 2.6.1 (xorg-server 1.9.3.902) fails because tcsh crashes
Hello Jeremy! There was an interesting failure after installation of the latest security patches. In tcsh's history file were items like: l /System/Library/Fonts/ otfinfo -i /System/Library/Fonts/儷黑\ Pro.ttf otfinfo -i /System/Library/Fonts/ヒラギノ明朝\ ProN\ W3.otf otfinfo -i /System/Library/Fonts/ヒラギノ明朝\ ProN\ W6.otf otfinfo -i /System/Library/Fonts/ヒラギノ角ゴ\ ProN\ W3.otf l /Library/Fonts/ which finally and at once led to Segmentation fault (core dumped) Exit 139 Other software failed as well, but Terminal, xterm, or the shells in GNU Emacs not... (Discovered by running /Applications/MacPorts/X11.app/ Contents/MacOS/X11 in Terminal.) Since it happens/happened on Leopard it's probably useless to report the tcsh behaviour as bug... -- Greetings Pete Real Time, adj.: Here and now, as opposed to fake time, which only occurs there and then.
Hey Peter, I'm not entirely sure what you are reporting here. What crashed, and how did you crash it? Did tcsh crash with 'cat ~/.tcsh_history' or similar? I'm confused. Do you have a crash report? Since this doesn't sound X11 related, please file a bug at http://bugreport.apple.com including the crash report. Send me an email off-list with the id of the bug, and I'll keep an eye on it. Thanks, Jeremy On Apr 23, 2011, at 1:02 PM, Peter Dyballa wrote:
Hello Jeremy!
There was an interesting failure after installation of the latest security patches. In tcsh's history file were items like:
l /System/Library/Fonts/
otfinfo -i /System/Library/Fonts/儷黑\ Pro.ttf
otfinfo -i /System/Library/Fonts/ヒラギノ明朝\ ProN\ W3.otf
otfinfo -i /System/Library/Fonts/ヒラギノ明朝\ ProN\ W6.otf
otfinfo -i /System/Library/Fonts/ヒラギノ角ゴ\ ProN\ W3.otf
l /Library/Fonts/
which finally and at once led to
Segmentation fault (core dumped) Exit 139
Other software failed as well, but Terminal, xterm, or the shells in GNU Emacs not... (Discovered by running /Applications/MacPorts/X11.app/Contents/MacOS/X11 in Terminal.) Since it happens/happened on Leopard it's probably useless to report the tcsh behaviour as bug...
-- Greetings
Pete
Real Time, adj.: Here and now, as opposed to fake time, which only occurs there and then.
_______________________________________________ Xquartz-dev mailing list Xquartz-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/xquartz-dev
Am 23.04.2011 um 22:15 schrieb Jeremy Huddleston:
What crashed, and how did you crash it?
Tcsh crashed. It crashed quite soon after clicking the icon in dock or invoking 'open ....X11.app', before the server could identify itself. From system.log: Apr 22 11:42:29 localhost ReportCrash[543]: Formulating crash report for process tcsh[521] Apr 22 11:42:29 localhost ReportCrash[543]: Saved crashreport to / Users/pete/Library/Logs/CrashReporter/ tcsh_2011-04-22-114228_Latsche.crash using uid: 501 gid: 501, euid: 501 egid: 501 Apr 22 11:42:29 localhost com.apple.launchd[199] ([0x0-0x23023].org.x.X11[521]): Exited abnormally: Segmentation fault Apr 22 11:46:25 localhost ReportCrash[624]: Formulating crash report for process tcsh[603] Apr 22 11:46:25 localhost ReportCrash[624]: Saved crashreport to / Users/pete/Library/Logs/CrashReporter/ tcsh_2011-04-22-114624_Latsche.crash using uid: 501 gid: 501, euid: 501 egid: 501 Apr 22 11:46:25 localhost com.apple.launchd[199] ([0x0-0x2a02a].org.macports.X11[603]): Exited abnormally: Segmentation fault In Console.app's "console messages" (or such) window the messages from X11 have disappeared and I don't in which file they are recorded – if at all!
Did tcsh crash with 'cat ~/.tcsh_history' or similar?
This does not belong to any of the statements in ~/.login or ~/. (t)cshrc. There must be some "replay", a way to integrate the old shell's history into the new one's history. With 'set verbose' this becomes visible.
Do you have a crash report?
Yes, a few, all for tcsh. -- Greetings Pete From error to error, one discovers the entire truth. - Sigmund Freud
Ok, well please file a bug report at http://bugreport.apple.com ... tcsh is unrelated to X11. Thanks, Jeremy On Apr 23, 2011, at 17:06, Peter Dyballa wrote:
Am 23.04.2011 um 22:15 schrieb Jeremy Huddleston:
What crashed, and how did you crash it?
Tcsh crashed. It crashed quite soon after clicking the icon in dock or invoking 'open ....X11.app', before the server could identify itself. From system.log:
Apr 22 11:42:29 localhost ReportCrash[543]: Formulating crash report for process tcsh[521] Apr 22 11:42:29 localhost ReportCrash[543]: Saved crashreport to /Users/pete/Library/Logs/CrashReporter/tcsh_2011-04-22-114228_Latsche.crash using uid: 501 gid: 501, euid: 501 egid: 501 Apr 22 11:42:29 localhost com.apple.launchd[199] ([0x0-0x23023].org.x.X11[521]): Exited abnormally: Segmentation fault
Apr 22 11:46:25 localhost ReportCrash[624]: Formulating crash report for process tcsh[603] Apr 22 11:46:25 localhost ReportCrash[624]: Saved crashreport to /Users/pete/Library/Logs/CrashReporter/tcsh_2011-04-22-114624_Latsche.crash using uid: 501 gid: 501, euid: 501 egid: 501 Apr 22 11:46:25 localhost com.apple.launchd[199] ([0x0-0x2a02a].org.macports.X11[603]): Exited abnormally: Segmentation fault
In Console.app's "console messages" (or such) window the messages from X11 have disappeared and I don't in which file they are recorded – if at all!
Did tcsh crash with 'cat ~/.tcsh_history' or similar?
This does not belong to any of the statements in ~/.login or ~/.(t)cshrc. There must be some "replay", a way to integrate the old shell's history into the new one's history. With 'set verbose' this becomes visible.
Do you have a crash report?
Yes, a few, all for tcsh.
-- Greetings
Pete
From error to error, one discovers the entire truth. - Sigmund Freud
_______________________________________________ Xquartz-dev mailing list Xquartz-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/xquartz-dev
participants (2)
-
Jeremy Huddleston
-
Peter Dyballa