| IDL Segmentation Fault [message #50398] |
Tue, 03 October 2006 08:51  |
Bill Anderson
Messages: 2
Registered: October 2006
|
Junior Member |
|
|
Hi,
Has anyone run into this problem? I have running IDL 6.2 student
edition for the past month with no problems on a MacPro Book (MacOS X
10.4) notebook. This weekend I updated my MacOS to 10.4.8 and now when
I try to run idl from X11, it crashes with a "Segmentation Fault".
/Users/wmandersonjr/idl
IDL Student Edition 6.2, Mac OS X (darwin ppc m32). (c) 2005, Research
Systems, Inc.
Segmentation fault
/Users/wmandersonjr/
Bill Anderson
|
|
|
|
|
|
| Re: IDL Segmentation Fault [message #50517 is a reply to message #50398] |
Wed, 04 October 2006 16:34  |
Karl Schultz
Messages: 341
Registered: October 1999
|
Senior Member |
|
|
On Wed, 04 Oct 2006 15:09:13 -0700, mankoff wrote:
> Karl Schultz wrote:
>> On Wed, 04 Oct 2006 09:06:26 -0700, mankoff wrote:
>>
>>> David Fanning wrote:
>>>> Bill Anderson writes:
>>>>
>>>> > Has anyone run into this problem? I have running IDL 6.2 student
>>>> > edition for the past month with no problems on a MacPro Book (MacOS X
>>>> > 10.4) notebook. This weekend I updated my MacOS to 10.4.8 and now when
>>>> > I try to run idl from X11, it crashes with a "Segmentation Fault".
>>>> >
>>>> > /Users/wmandersonjr/idl
>>>> > IDL Student Edition 6.2, Mac OS X (darwin ppc m32). (c) 2005, Research
>>>> > Systems, Inc.
>>>> > Segmentation fault
>>>> > /Users/wmandersonjr/
>>>>
>>>> You might find this article helpful:
>>>>
>>>> http://www.dfanning.com/tips/maccrash.html
>>>>
>>>> Also, we discussed this problem right here less than two weeks
>>>> ago, it seems to me. Check the archives.
>>>>
>>>
>>>
>>> I've read that article and searched the archives. I'm using IDL 5.6 on
>>> a Intel MacBook. X11 programs work fine, but IDL is segfaulting
>>> nonetheless.
>>>
>>> If DISPLAY is :0.0 then xeyes works and IDL segfaults
>>>
>>> If DISPLAY is 0:0 then IDL will run but provides error messages when
>>> trying to access the display, like so:
>>>
>>> _X11TransSocketINETConnect() can't get address for 0:6000: No address
>>> associated with nodename
>>> % Unable to connect to X Windows display: 0:0
>>>
>>>
>>> Any advice?
>>>
>>> This just started yesterday when I upgraded to 10.4.8.
>>>
>>> -k.
>>
>> Yes, I've been looking at this recently, and have collected some hopefully
>> useful information.
>>
>> IDL PPC binaries of any release now appear to crash when running on an
>> Intel Mac under Rosetta emulation with OS X 10.4.8. The problem didn't
>> occur with OS X 10.4.7. The crash logs indicate a crash in libXt. Since
>> the *only* change made to the environment where I observed all of this was
>> upgrading from 10.4.7 to 10.4.8, I am inclined to suspect the Apple update
>> to 10.4.8.
>>
>> Some web searching reveals that there are more than a few problems with
>> the 10.4.8 upgrade on Intel Macs. One person reported a similar crash
>> with Matlab 7.1 under the same conditions. The report indicated that the
>> Matlab crashes started after the upgrade to 10.4.8 was applied. Same
>> situation, same problem, I think. One could also extend this thought to
>> the possibility that any PPC binary X11 application running under Rosetta
>> on an Intel based OS X 10.4.8 might crash.
>>
>> Therefore IDL users of versions prior to 6.3 probably should not upgrade
>> their Intel Macs to 10.4.8.
>>
>> IDL 6.3 users should really get the Intel binaries for IDL that are
>> available from ITTVIS. Not only would this relieve this particular 10.4.8
>> problem, but the Intel binaries run faster on the Intel Mac.
>>
>> The PPC-based hardware does not seem to be adversely affected by this OS X
>> upgrade.
>>
>> I'm going to go ahead and report this problem to Apple, and all we can do
>> is hope that they'll take the time from the Leopard schedule to release a
>> patch for this seemingly defective OS X upgrade.
>>
>> That's the best I can do for now,
>>
>> Karl
>
> Thanks for taking this up with Apple. Any luck just swapping out libXt
> with the previous version? I don't have access to my backup disk for
> another 10 days while I travel so I cannot test this.
I wouldn't even try it, because even if it worked, nobody would want
to do anything important in that sort of environment. I would also think
that more than just that one module is involved. And I didn't see any
crashes when using a VNC server on the same box, so the X server itself
may be part of the problem.
And by the way, I did copy the /usr/X11R6/bin/xclock binary from a ppc OS
X machine and it crashed on the intel 10.4.8 machine, as I suspected it
would. That's the way I filed the bug with Apple.
Karl
|
|
|
|
| Re: IDL Segmentation Fault [message #50520 is a reply to message #50398] |
Wed, 04 October 2006 15:09 |
mankoff
Messages: 131
Registered: March 2004
|
Senior Member |
|
|
Karl Schultz wrote:
> On Wed, 04 Oct 2006 09:06:26 -0700, mankoff wrote:
>
>> David Fanning wrote:
>>> Bill Anderson writes:
>>>
>>>> Has anyone run into this problem? I have running IDL 6.2 student
>>>> edition for the past month with no problems on a MacPro Book (MacOS X
>>>> 10.4) notebook. This weekend I updated my MacOS to 10.4.8 and now when
>>>> I try to run idl from X11, it crashes with a "Segmentation Fault".
>>>>
>>>> /Users/wmandersonjr/idl
>>>> IDL Student Edition 6.2, Mac OS X (darwin ppc m32). (c) 2005, Research
>>>> Systems, Inc.
>>>> Segmentation fault
>>>> /Users/wmandersonjr/
>>>
>>> You might find this article helpful:
>>>
>>> http://www.dfanning.com/tips/maccrash.html
>>>
>>> Also, we discussed this problem right here less than two weeks
>>> ago, it seems to me. Check the archives.
>>>
>>
>>
>> I've read that article and searched the archives. I'm using IDL 5.6 on
>> a Intel MacBook. X11 programs work fine, but IDL is segfaulting
>> nonetheless.
>>
>> If DISPLAY is :0.0 then xeyes works and IDL segfaults
>>
>> If DISPLAY is 0:0 then IDL will run but provides error messages when
>> trying to access the display, like so:
>>
>> _X11TransSocketINETConnect() can't get address for 0:6000: No address
>> associated with nodename
>> % Unable to connect to X Windows display: 0:0
>>
>>
>> Any advice?
>>
>> This just started yesterday when I upgraded to 10.4.8.
>>
>> -k.
>
> Yes, I've been looking at this recently, and have collected some hopefully
> useful information.
>
> IDL PPC binaries of any release now appear to crash when running on an
> Intel Mac under Rosetta emulation with OS X 10.4.8. The problem didn't
> occur with OS X 10.4.7. The crash logs indicate a crash in libXt. Since
> the *only* change made to the environment where I observed all of this was
> upgrading from 10.4.7 to 10.4.8, I am inclined to suspect the Apple update
> to 10.4.8.
>
> Some web searching reveals that there are more than a few problems with
> the 10.4.8 upgrade on Intel Macs. One person reported a similar crash
> with Matlab 7.1 under the same conditions. The report indicated that the
> Matlab crashes started after the upgrade to 10.4.8 was applied. Same
> situation, same problem, I think. One could also extend this thought to
> the possibility that any PPC binary X11 application running under Rosetta
> on an Intel based OS X 10.4.8 might crash.
>
> Therefore IDL users of versions prior to 6.3 probably should not upgrade
> their Intel Macs to 10.4.8.
>
> IDL 6.3 users should really get the Intel binaries for IDL that are
> available from ITTVIS. Not only would this relieve this particular 10.4.8
> problem, but the Intel binaries run faster on the Intel Mac.
>
> The PPC-based hardware does not seem to be adversely affected by this OS X
> upgrade.
>
> I'm going to go ahead and report this problem to Apple, and all we can do
> is hope that they'll take the time from the Leopard schedule to release a
> patch for this seemingly defective OS X upgrade.
>
> That's the best I can do for now,
>
> Karl
Thanks for taking this up with Apple. Any luck just swapping out libXt
with the previous version? I don't have access to my backup disk for
another 10 days while I travel so I cannot test this.
|
|
|
|
| Re: IDL Segmentation Fault [message #50524 is a reply to message #50398] |
Wed, 04 October 2006 11:26 |
Karl Schultz
Messages: 341
Registered: October 1999
|
Senior Member |
|
|
On Wed, 04 Oct 2006 09:06:26 -0700, mankoff wrote:
> David Fanning wrote:
>> Bill Anderson writes:
>>
>>> Has anyone run into this problem? I have running IDL 6.2 student
>>> edition for the past month with no problems on a MacPro Book (MacOS X
>>> 10.4) notebook. This weekend I updated my MacOS to 10.4.8 and now when
>>> I try to run idl from X11, it crashes with a "Segmentation Fault".
>>>
>>> /Users/wmandersonjr/idl
>>> IDL Student Edition 6.2, Mac OS X (darwin ppc m32). (c) 2005, Research
>>> Systems, Inc.
>>> Segmentation fault
>>> /Users/wmandersonjr/
>>
>> You might find this article helpful:
>>
>> http://www.dfanning.com/tips/maccrash.html
>>
>> Also, we discussed this problem right here less than two weeks
>> ago, it seems to me. Check the archives.
>>
>
>
> I've read that article and searched the archives. I'm using IDL 5.6 on
> a Intel MacBook. X11 programs work fine, but IDL is segfaulting
> nonetheless.
>
> If DISPLAY is :0.0 then xeyes works and IDL segfaults
>
> If DISPLAY is 0:0 then IDL will run but provides error messages when
> trying to access the display, like so:
>
> _X11TransSocketINETConnect() can't get address for 0:6000: No address
> associated with nodename
> % Unable to connect to X Windows display: 0:0
>
>
> Any advice?
>
> This just started yesterday when I upgraded to 10.4.8.
>
> -k.
Yes, I've been looking at this recently, and have collected some hopefully
useful information.
IDL PPC binaries of any release now appear to crash when running on an
Intel Mac under Rosetta emulation with OS X 10.4.8. The problem didn't
occur with OS X 10.4.7. The crash logs indicate a crash in libXt. Since
the *only* change made to the environment where I observed all of this was
upgrading from 10.4.7 to 10.4.8, I am inclined to suspect the Apple update
to 10.4.8.
Some web searching reveals that there are more than a few problems with
the 10.4.8 upgrade on Intel Macs. One person reported a similar crash
with Matlab 7.1 under the same conditions. The report indicated that the
Matlab crashes started after the upgrade to 10.4.8 was applied. Same
situation, same problem, I think. One could also extend this thought to
the possibility that any PPC binary X11 application running under Rosetta
on an Intel based OS X 10.4.8 might crash.
Therefore IDL users of versions prior to 6.3 probably should not upgrade
their Intel Macs to 10.4.8.
IDL 6.3 users should really get the Intel binaries for IDL that are
available from ITTVIS. Not only would this relieve this particular 10.4.8
problem, but the Intel binaries run faster on the Intel Mac.
The PPC-based hardware does not seem to be adversely affected by this OS X
upgrade.
I'm going to go ahead and report this problem to Apple, and all we can do
is hope that they'll take the time from the Leopard schedule to release a
patch for this seemingly defective OS X upgrade.
That's the best I can do for now,
Karl
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| [OT] Re: IDL Segmentation Fault [message #51237 is a reply to message #50398] |
Fri, 03 November 2006 11:45 |
Paul Van Delst[1]
Messages: 1157
Registered: April 2002
|
Senior Member |
|
|
Kenneth Bowman wrote:
> In article <eig2ai$3g4$1@news.nems.noaa.gov>,
> Paul van Delst <Paul.vanDelst@noaa.gov> wrote:
>
>> Nah, my macbook is a pure work machine. The less crud I have on it the
>> better. However,
>> work efficiency would be *greatly* enhanced if multiple desktops were
>> available like in
>> stock RH linux distros[*] Or if OSX was an actual Unix OS. Or, most
>> importantly, if the
>> darn thing didn't crash several times a day.[+]
>>
>> Now, the iMac sitting next to my macbook, that's another matter..... it only
>> crashes once
>> a week or so and iTunes is up-to-doodly-date. :o)
>
> That seems like a lot of crashes. I won't say mine never crashes, but it is a
> very rare event.
Yeah it's a lot of crashes. This was my first ever foray into the non-PC linux world and,
boy, it makes windows machines look supa-stable. I reboot my linux desktop about, oh,
twice a year -- that the reliability I'm used to. Granted laptops are another ball of wax,
but even there I think once a month is too often. Macbook pro constant crashes are very
common (google it.. I was amazed). The sad thing is that the first piece of hardware that
Apple produced that wasn't apparently rock-solid is the one I started with. Good timing,
hey? :o)
> I never sleep my desktop Mac. It causes problems with the network file mounts.
>
> I sleep my Powerbook every time I move it from work to home. Every couple of
> weeks it gets tired of the constant network changes and quits connecting, so I
> restart it. It helps to be sure that volumes are unmounted before sleeping.
There are multiple issues with the sleeping/crashing problems with Intel macbook pros. By
far and away the most common theory is that, in some cases, the temperature sensor wires
are too close to the CPU heat sink and, since these machines run hot, sometimes the wire
casing melts away causing intermittent shorting and the machine shuts down. Googling this
topic will get you many hits. I have had one person tell me about a lid-latch issue -
somehow the sensor that detects the laptop is open is tripped even when it's closed and
the thing wakes up while in your laptop back .. and is very hot when it comes out. In
other cases, not turning off the bluetooth auto-detect may be causing the laptops to wake
up en route somewhere and again, it's hot when it comes out of the bag.
I haven't yet figured out why my laptop was crashing contantly, but I suspect its hotness.
It only happens when it's connected to all my other bits at home (display, external drive,
wireless mouse/keyboard); on travel using it as an actual laptop it's fine. At home,
making it hibernate rather than sleep helped - the inconvenience of having to press the
"on" button and wait about 2-3 minutes for it to wake up is acceptable compared to the
alternative.
Anyway.....
cheers,
paulv
--
Paul van Delst Ride lots.
CIMSS @ NOAA/NCEP/EMC Eddy Merckx
Ph: (301)763-8000 x7748
Fax:(301)763-8545
|
|
|
|
| Re: IDL Segmentation Fault [message #51239 is a reply to message #50398] |
Fri, 03 November 2006 10:57 |
K. Bowman
Messages: 330
Registered: May 2000
|
Senior Member |
|
|
In article <eig2ai$3g4$1@news.nems.noaa.gov>,
Paul van Delst <Paul.vanDelst@noaa.gov> wrote:
> Nah, my macbook is a pure work machine. The less crud I have on it the
> better. However,
> work efficiency would be *greatly* enhanced if multiple desktops were
> available like in
> stock RH linux distros[*] Or if OSX was an actual Unix OS. Or, most
> importantly, if the
> darn thing didn't crash several times a day.[+]
>
> Now, the iMac sitting next to my macbook, that's another matter..... it only
> crashes once
> a week or so and iTunes is up-to-doodly-date. :o)
That seems like a lot of crashes. I won't say mine never crashes, but it is a
very rare event.
I never sleep my desktop Mac. It causes problems with the network file mounts.
I sleep my Powerbook every time I move it from work to home. Every couple of
weeks it gets tired of the constant network changes and quits connecting, so I
restart it. It helps to be sure that volumes are unmounted before sleeping.
Ken Bowman
|
|
|
|
| Re: IDL Segmentation Fault [message #51241 is a reply to message #51043] |
Fri, 03 November 2006 10:38 |
Paul Van Delst[1]
Messages: 1157
Registered: April 2002
|
Senior Member |
|
|
David Fanning wrote:
> Paul van Delst writes:
>
>> o.k. thanks, I'll doublecheck. (Last time it popped up all I saw listed were iTunes and
>> Garageband ;o)
>
> Well, get those, too. Otherwise the "work efficiency" numbers
> are going to be all shot to hell. :-)
Nah, my macbook is a pure work machine. The less crud I have on it the better. However,
work efficiency would be *greatly* enhanced if multiple desktops were available like in
stock RH linux distros[*] Or if OSX was an actual Unix OS. Or, most importantly, if the
darn thing didn't crash several times a day.[+]
Now, the iMac sitting next to my macbook, that's another matter..... it only crashes once
a week or so and iTunes is up-to-doodly-date. :o)
paulv
[*] I know there are multi-desktop apps available for Apples - I've tried a couple and
quickly uninstalled them.
[+] Problem partially solved via making the thing hibernate rather than sleep.
--
Paul van Delst Ride lots.
CIMSS @ NOAA/NCEP/EMC Eddy Merckx
Ph: (301)763-8000 x7748
Fax:(301)763-8545
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
