On Sep 14, 2008, at 1:49 AM, Glynn Clements wrote:
Michael Barton wrote:
Attached is the crashlog
There is something a bit odd with the header information. It has the
right path for my MacPython version installation, but the version is
for the Apple system Python. I wonder if this is along the same lines
as the issue that was killing vdigit.
If it's mixing binaries for different Python versions, that isn't
going to work.
Certainly, the crash dump is consistent with that scenario, i.e.
crashing while dlopen()ing a shared library.
Remind me again: why can't you use the system Python? Is wxPython not
available for the system Python?
The system Python is 2.5.0 alpha. I was already using 2.5.1 before I
upgraded to OS X 10.5 with the alpha version of 2.5.0 because prior to
10.5, Apple shipped only 2.3 with its OS. I don't know why. One of the
mysteries of Cupertino.
Binary Images:
0x13fe7000 - 0x13fe7ff1 +libXau.6.dylib ??? (???)
<af0fefbbf38efd4df94bedea64d5019d> /usr/X11/lib/libXau.6.dylib
0x14758000 - 0x1475dffc +libSM.6.dylib ??? (???)
<da2933333b791701efb3878166c35435> /usr/X11/lib/libSM.6.dylib
0x147e6000 - 0x147f7ff7 +libICE.6.dylib ??? (???)
<68bd0c63da68b6c30273693c7b775c4f> /usr/X11/lib/libICE.6.dylib
0x16012000 - 0x1605dff8 +libXt.6.dylib ??? (???)
<09f2a2bdce4a8d5c4b753254435c52ea> /usr/X11/lib/libXt.6.dylib
0x16072000 - 0x1615dfe7 +libX11.6.dylib ??? (???)
<b17988a7d0432be8daf271882b9f1d45> /usr/X11/lib/libX11.6.dylib
0x17442000 - 0x17444fef +libXdmcp.6.dylib ??? (???)
<a12913daa7d2b4efb341cb698f4182fa> /usr/X11/lib/libXdmcp.6.dylib
What are those doing in there?
There should be no x11 calls. Is this something hard coded for Linux
somewhere?
More importantly:
0x1de6000 - 0x2483607 +libwx_macud-2.8.0.dylib ??? (???) /usr/
local/lib/wxPython-unicode-2.8.8.1/lib/libwx_macud-2.8.0.dylib
The date on these libraries seem to be associate them with the system
Python install
0x1586c000 - 0x15d39fff libwx_macud-2.8.0.dylib ??? (???)
<cfd5a59e5c9ce50c5a7a8888acfbd15d> /usr/lib/libwx_macud-2.8.0.dylib
These are associated with the installation of the current wxPython 2.8.8
Is it actually loading two different libwx_macud-2.8.0.dylib
libraries? That certainly doesn't look good.
--
Glynn Clements <[EMAIL PROTECTED]>
_______________________________________________
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev