|
From: Mathieu M. <mat...@ki...> - 2004-02-06 18:43:53
|
Hi all, Does anyone of you use the fglrx driver and valgrind ? I am having bad X froze. valgrind is working really fine with console type programm, and it also doing fine when using nvidia driver (on another machine with a 3d graphics program). Is there a way to track the problem ? Thanks Mathieu Using fedora, linux knl: 2.4.22-1.2115.nptlsmp $ fglrxinfo display: :0.0 screen: 0 OpenGL vendor string: ATI Technologies Inc. OpenGL renderer string: RADEON 9800 Pro x86/SSE2 OpenGL version string: 1.3 (X4.3.0-3.7.0) |
|
From: Leonard m. <spa...@ya...> - 2004-02-06 19:36:13
|
Mathieu Malaterre: > Does anyone of you use the fglrx driver and valgrind ? I am having bad X froze. valgrind is working really fine with console type programm, and it also doing fine when using nvidia driver (on another machine with a 3d graphics program). Is there a way to track the problem ? Yes, I experience exactly the same problem on programs linked with the ATI libGL.so on Linux. The whole machine locks hard after about 20-30 seconds! I hadn't conclusively established that it was the ATI driver but I guess you have. I'll help track this as well if one of the valgrind folks can suggest a few things to try. I greatly miss being able to use valgrind on my app. Mesa hasn't caught up with the features we're using, so linking with Mesa's libGL is unfortunately not a work-around. __________________________________ Do you Yahoo!? Yahoo! Finance: Get your refund fast by filing online. http://taxes.yahoo.com/filing.html |
|
From: Mathieu M. <mat...@ki...> - 2004-02-06 20:30:34
|
> Yes, I experience exactly the same problem on programs linked with the
> ATI libGL.so on Linux. The whole machine locks hard after about 20-30
> seconds!
Same here ! the display is fine, but if I hit a key ('q' to quit the
app), then after about 20s the whole machine locks.
BTW I was able to open the display, render my 3d structure, and quit
without problem, the sole difference was that I didn't had to hit any
key to close. So my guess is now this is a mixture of: keyborad event +
ATI libGL.so + valgrind.
Comments welcome
Mathieu
|
|
From: Nicholas N. <nj...@ca...> - 2004-02-07 18:03:31
|
On Fri, 6 Feb 2004, Mathieu Malaterre wrote:
> > Yes, I experience exactly the same problem on programs linked with the
> > ATI libGL.so on Linux. The whole machine locks hard after about 20-30
> > seconds!
>
> Same here ! the display is fine, but if I hit a key ('q' to quit the
> app), then after about 20s the whole machine locks.
Can one of you please file a bug at bugs.kde.org/enter_valgrind_bug.cgi?
Please include as much relevant info as possible.
N
|
|
From: Leonard m. <spa...@ya...> - 2004-02-10 01:27:02
|
--- Mathieu Malaterre <mat...@ki...> wrote:
> Same here ! the display is fine, but if I hit a key ('q' to
> quit the app), then after about 20s the whole machine locks.
>
> BTW I was able to open the display, render my 3d structure, and
> quit without problem, the sole difference was that I didn't
> had to hit any key to close. So my guess is now this is a
> mixture of: keyborad event
Well, I can say with pretty high confidence that it has nothing to do
with the keyboard. Our app won't even come up and start rendering,
whether I touch the keyboard or not. It just locks the whole machine
hard.
Could you trace down what your app is doing in response to that key?
Maybe its touching some kernel sysctl or driver API call that's causing
valgrind to lose its mind.
__________________________________
Do you Yahoo!?
Yahoo! Finance: Get your refund fast by filing online.
http://taxes.yahoo.com/filing.html
|