Re: getting Tiger's X11 running on Leopard
Re: getting Tiger's X11 running on Leopard
- Subject: Re: getting Tiger's X11 running on Leopard
- From: Josh Colwell <email@hidden>
- Date: Mon, 26 Nov 2007 11:25:53 -0500
Here is the first third or so of the Report output. I don't understand
the information in here so I'm not sure if this is all the relevant
information, but I didn't want to flood e-mail with the full thing
unless necessary...
Josh
Process: Xquartz [269]
Path: /usr/X11/X11.app/Contents/MacOS/X11
Identifier: org.x.X11
Version: 2.0 (???)
Build Info: X11server-460000~4
Code Type: X86 (Native)
Parent Process: X11 [268]
Date/Time: 2007-11-26 11:23:18.768 -0500
OS Version: Mac OS X 10.5.1 (9B18)
Report Version: 6
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x00000000affddf44
Crashed Thread: 1
Thread 0:
0 libSystem.B.dylib 0x91eda8e6 mach_msg_trap + 10
1 libSystem.B.dylib 0x91ee20dc mach_msg + 72
2 com.apple.CoreFoundation 0x900a00fe CFRunLoopRunSpecific +
1806
3 com.apple.CoreFoundation 0x900a0d38 CFRunLoopRunInMode + 88
4 com.apple.HIToolbox 0x9629e8a4
RunCurrentEventLoopInMode + 283
5 com.apple.HIToolbox 0x9629e6bd ReceiveNextEventCommon +
374
6 com.apple.HIToolbox 0x9629e531
BlockUntilNextEventMatchingListInMode + 106
7 com.apple.AppKit 0x90ae5d5b _DPSNextEvent + 657
8 com.apple.AppKit 0x90ae56a0 -[NSApplication
nextEventMatchingMask:untilDate:inMode:dequeue:] + 128
9 com.apple.AppKit 0x90ade6d1 -[NSApplication run] + 795
10 Xquartz 0x00012cbc X11ApplicationMain + 658
11 Xquartz 0x00015a1e X11ControllerMain + 38
12 Xquartz 0x0001a504 DarwinHandleGUI + 672
13 Xquartz 0x00098e77 main + 59
14 Xquartz 0x000020a2 start + 54
Thread 1 Crashed:
0 Xquartz 0x00045929 miFillGeneralPoly + 155
1 Xquartz 0x00044ff7 miFillPolygon + 416
2 Xquartz 0x00148aa5 damageFillPolygon + 816
3 Xquartz 0x000228a7 RootlessFillPolygon + 923
4 Xquartz 0x00082374 ProcFillPoly + 579
5 Xquartz 0x000fd61f XaceCatchDispatchProc +
146
6 Xquartz 0x0007df71 Dispatch + 640
7 Xquartz 0x000995bd main + 1921
8 Xquartz 0x0001a25c server_thread + 59
9 libSystem.B.dylib 0x91f0b075 _pthread_start + 321
10 libSystem.B.dylib 0x91f0af32 thread_start + 34
Thread 2:
0 libSystem.B.dylib 0x91ee1ace __semwait_signal + 10
1 libSystem.B.dylib 0x91f0bced pthread_cond_wait
$UNIX2003 + 73
2 libXplugin.1.dylib 0x00406cbe _xp_async_dequeue + 41
3 libXplugin.1.dylib 0x00406d24 _xp_async_thread + 54
4 libSystem.B.dylib 0x91f0b075 _pthread_start + 321
5 libSystem.B.dylib 0x91f0af32 thread_start + 34
Thread 1 crashed with X86 Thread State (32-bit):
eax: 0xb00c4110 ebx: 0x00148781 ecx: 0xb00c45a0 edx: 0xaffddf50
edi: 0x0002250c esi: 0x00000000 ebp: 0xb00c48d8 esp: 0xaffddf30
ss: 0x0000001f efl: 0x00010286 eip: 0x00045929 cs: 0x00000017
ds: 0x0000001f es: 0x0000001f fs: 0x0000001f gs: 0x00000037
cr2: 0xaffddf44
On Nov 26, 2007, at 11:16 AM, Jeremy Huddleston wrote:
On Nov 26, 2007, at 08:08, Josh Colwell wrote:
Hi, yes, I've updated to IDL 6.4.1. That resolved one issue so I
could at least run IDL, but I now get semi-predictable X11 crashes
when working with modestly large arrays of data (and in the most
recent case, a simple iPlot tool when changing settings).
Interesting... X11 shouldn't care at all about the amount of data
IDL is processing... it really is just concerned with the
visualization of the data. Do you have any backtraces you can show
us (copy-pasted from 'Report' when X11 crashes)?
--Jeremy
--------------------------------------------
Josh Colwell
Department of Physics
University of Central Florida
Orlando FL 32816-2385
email@hidden
407-823-5208 (temporary)
http://physics.ucf.edu/~jcolwell
--------------------------------------------
_______________________________________________
Do not post admin requests to the list. They will be ignored.
X11-users mailing list (email@hidden)
This email sent to email@hidden