View previous topic :: View next topic |
Author |
Message |
lozzer
Joined: 27 Jun 2007 Posts: 49
|
Posted: Tue Jul 13, 2010 10:04 am Post subject: Re: |
|
|
Robert wrote: | Just to be clear on this ... this issue does affect 32-bit Window as well as 64-bit? |
Haven't a clue. Problems currently on 64-bit with ATI as mentioned in my earlier post. I don't know of any customers who are buying 32-bit systems anymore. _________________ Lozzer |
|
Back to top |
|
|
Robert
Joined: 29 Nov 2006 Posts: 445 Location: Manchester
|
Posted: Tue Jul 13, 2010 4:43 pm Post subject: |
|
|
Can you download this and run it:
http://www.silverfrost.com/public_downloads/wglCreateContext.exe
It will need salflibc.dll on the path. It checks that it can talk to the OpenGL subsystem. The traceback from lozzer suggested that maybe it couldn't see it.
Sebastian: are you still saying that it is a FP control word issue? I have stepped through the call that the above .exe makes and there are no FPCW changes. If the CW was being changed as you said it would cause a big problem. |
|
Back to top |
|
|
Sebastian
Joined: 20 Feb 2008 Posts: 177
|
Posted: Tue Jul 13, 2010 6:46 pm Post subject: |
|
|
Quote: | I have stepped through the call that the above .exe makes and there are no FPCW changes. |
It's the default fpu CW setting (is that even specified in the EXE/PE header??) of a ftn95 compiled executable which leaves the underflow exception unmasked.
Thanks for looking into this! |
|
Back to top |
|
|
Sebastian
Joined: 20 Feb 2008 Posts: 177
|
Posted: Wed Jul 14, 2010 9:51 am Post subject: |
|
|
Quote: | It checks that it can talk to the OpenGL subsystem. The traceback from lozzer suggested that maybe it couldn't see it. |
The call works fine here and returns a non-null address. In general there's no problem with the wglCreateContext functionality per se on these systems/ATI drivers, other OpenGL applications work fine, all have to create a context using this function. |
|
Back to top |
|
|
lozzer
Joined: 27 Jun 2007 Posts: 49
|
Posted: Wed Jul 14, 2010 10:42 am Post subject: Re: |
|
|
Robert wrote: | Can you download this and run it:
http://www.silverfrost.com/public_downloads/wglCreateContext.exe
It will need salflibc.dll on the path. It checks that it can talk to the OpenGL subsystem. The traceback from lozzer suggested that maybe it couldn't see it.
Sebastian: are you still saying that it is a FP control word issue? I have stepped through the call that the above .exe makes and there are no FPCW changes. If the CW was being changed as you said it would cause a big problem. |
I'm completely lost now. Is this program supposed to work on a client's PC? I've tried running it on mine and I get what appears to be a command box appearing very briefly and then it disappears. _________________ Lozzer |
|
Back to top |
|
|
Robert
Joined: 29 Nov 2006 Posts: 445 Location: Manchester
|
Posted: Wed Jul 14, 2010 10:59 am Post subject: |
|
|
You need to run it from a command prompt (otherwise the message disappears). It should be run on a machine that has the problem. |
|
Back to top |
|
|
Sebastian
Joined: 20 Feb 2008 Posts: 177
|
Posted: Wed Jul 14, 2010 11:16 am Post subject: |
|
|
Quote: | Is this program supposed to work on a client's PC? |
Yes. It is supposed to *not* crash as it only queries a function and does not execute it. |
|
Back to top |
|
|
lozzer
Joined: 27 Jun 2007 Posts: 49
|
Posted: Wed Jul 14, 2010 1:48 pm Post subject: Re: |
|
|
Robert wrote: | You need to run it from a command prompt (otherwise the message disappears). It should be run on a machine that has the problem. |
Okay, have tried it and on my PC gives an address. I am assuming that on a computer which has the problem it would give en error? _________________ Lozzer |
|
Back to top |
|
|
Sebastian
Joined: 20 Feb 2008 Posts: 177
|
Posted: Wed Jul 14, 2010 2:49 pm Post subject: |
|
|
Like I've already said, I tested it on Win7+ATI graphics card and it behaves as expected, i.e. does not crash and prints out the address of the wglCreateContext function. |
|
Back to top |
|
|
Robert
Joined: 29 Nov 2006 Posts: 445 Location: Manchester
|
Posted: Thu Jul 15, 2010 10:41 am Post subject: |
|
|
I have tried the OpenGL examples on a Win 7 x64 bit system with an ATI card. However, it was an oldish card and the examples ran okay.
Sebastian, can you post details of the crashes you see: tracebacks preferably from within salflibc.
Additionally, does the issue manifest itself through an RDP connection? If it does, is someone willing to let me have a debug via such a connection? |
|
Back to top |
|
|
Sebastian
Joined: 20 Feb 2008 Posts: 177
|
Posted: Thu Jul 15, 2010 11:02 am Post subject: |
|
|
Quote: | I have tried the OpenGL examples on a Win 7 x64 bit system with an ATI card. |
Only newer models are affected (ATI Radeon HD 5770 here, also see lozzer's list), we could not reproduce it with older models either.
Quote: | Sebastian, can you post details of the crashes you see: tracebacks preferably from within salflibc. |
The messages are not too helpful, for our main OpenGL application (Win7 message) it's an Access violation at instruction address 0, reading from 0. The small OpenGL test application (sources above, plain %og) just hangs and triggers some Win7 timeout.
Maybe lozzer has a more useful error message on the systems he tested his application.
When running the applications under an external debugger (OllyDbg) it halts at the fpu exception inside the ATI opengl driver. I can try to produce some screenshots of such a debugging session (salflibc's OpenGL window proc up to the wglCreateContext call) if that'd be helpful.
Quote: | Additionally, does the issue manifest itself through an RDP connection? |
I don't think RDP connections from outside are possible here, but I'll check that.
Thank you! |
|
Back to top |
|
|
lozzer
Joined: 27 Jun 2007 Posts: 49
|
Posted: Wed Jul 21, 2010 8:43 am Post subject: |
|
|
Has anyone at Silverfrost done any more about this one? _________________ Lozzer |
|
Back to top |
|
|
Robert
Joined: 29 Nov 2006 Posts: 445 Location: Manchester
|
Posted: Wed Jul 21, 2010 8:08 pm Post subject: |
|
|
> Additionally, does the issue manifest itself through an RDP connection? If it does, is someone willing to let me have a debug via such a connection?
We offered to debug it on a failing machine. |
|
Back to top |
|
|
Sebastian
Joined: 20 Feb 2008 Posts: 177
|
Posted: Wed Jul 21, 2010 8:20 pm Post subject: |
|
|
We cannot provide remote access to our machines (maybe somebody else can arrange that, but always tricky).
What/how do you intend to debug that? sdbg surely won't get you far. As already mentioned above I can provide e.g. screenshots of a low-level debug session depicting the problem spots. Or you can post details of what information you need/how you want to get them. |
|
Back to top |
|
|
Robert
Joined: 29 Nov 2006 Posts: 445 Location: Manchester
|
Posted: Wed Jul 21, 2010 10:43 pm Post subject: |
|
|
Please send all the information you can. |
|
Back to top |
|
|
|