Re: 2.6.3.rc1 Issue
Re: 2.6.3.rc1 Issue
- Subject: Re: 2.6.3.rc1 Issue
- From: Jeremy Huddleston <email@hidden>
- Date: Tue, 31 May 2011 13:22:32 -0700
I have a fix for this which will be in the final 2.6.3 release. Thanks for reporting.
--Jeremy
On May 31, 2011, at 10:24, Jeremy Huddleston wrote:
> So this is in our indirect GLX code.
>
> Is it reproducible? Can you try other GLX applications? Please try others which are freely available, so I can hopefully reproduce it.
>
> Thanks,
> Jeremy
>
> Thread 2 Crashed:
> 0 X11.bin 0x0000000100118293 __glXAquaScreenCreateContext + 684
> 1 X11.bin 0x00000001001315b0 DoCreateContext + 163
> 2 X11.bin 0x000000010013509f __glXDispatch + 211
> 3 X11.bin 0x00000001000c7dad Dispatch + 785
> 4 X11.bin 0x00000001000b97e5 dix_main + 1022
> 5 X11.bin 0x00000001000122bc server_thread + 50
> 6 libSystem.B.dylib 0x00007fff836554f6 _pthread_start + 331
> 7 libSystem.B.dylib 0x00007fff836553a9 thread_start + 13
>
>
> On May 31, 2011, at 07:58, Weller, Robert A wrote:
>
>> Jeremy,
>>
>> Report. Sure. Below. I just didn't want to spam the whole list with it.
>>
>> I apologize for not being able to give you more, but debugging at this system level is not one of my strong suits. If the report below that popped up when the failure happened is not revealing, my colleague Prof. Mendenhall, copied above, can probably help me get more specific information. By the way, the window that popped up with this report said that it was being sent to Apple, so I may have clicked to provide at least one of these to you (Apple) directly. The failure happened when I executed commands that should result in the opening of a graphic window on the remote machine. I repeated the procedure three or four times including once after a reboot of the client machine. I should have, but did not attempt to run anything else such as gears. I was in a hurry. The Geant4 program failed predictably the same way each time. Since I reinstalled 2.6.2 there have been no further incidents.
>>
>> If you need me to, I can reinstall 2.6.3-rc1 and get Marcus to help me with whatever we need to do to assist you to track this down. I know that it is possible that there could be some issue with my machine. However, it is the case that running the same Geant4 program locally did not produce the same crash.
>>
>> Thanks,
>> Bob Weller
>> Vanderbilt
>>
>>
>> On May 30, 2011, at 2:45 AM, Jeremy Huddleston wrote:
>>
>>> Can you please attach the crash report? There's not really anything to go on without it.
>>>
>>> Thanks.
>>>
>>> On May 29, 2011, at 10:09, Weller, Robert A wrote:
>>>
>>>> I have just discovered that XQuartz 2.6.3-rc1 crashes when I attempt to run a program on our linux cluster that uses X graphics. After observing XQuartz crash on my Mac three times repeatably at the same place in the code, I reverted to 2.6.2 and everything was ok again.
>>>>
>>>> Other than reporting that the remote program is based on the high-energy physics Geant4.9.4 code, and that everything on my Mac is up to date, I have no idea how to further describe this, other than by the crash report that was generated when the error occurred. I've save it, in case it is useful to someone familiar with reading them.
>>>>
>>>> Has anyone else seen this behavior with XQuartz 2.6.3-rc1 when using Geant4 with Linux and Darwin? By the way, when the identical Geant4 code is both run and locally on my Mac, the error does not occur.
>>>>
>>>> Thanks,
>>>> Robert Weller
>>>> Vanderbilt University _______________________________________________
>>>> Do not post admin requests to the list. They will be ignored.
>>>> X11-users mailing list (email@hidden)
>>>>
>>>> This email sent to email@hidden
>>>>
>>>
>>>
>>
>> <x-11.crash.txt>
>
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> X11-users mailing list (email@hidden)
>
> This email sent to email@hidden
>
_______________________________________________
Do not post admin requests to the list. They will be ignored.
X11-users mailing list (email@hidden)
This email sent to email@hidden