|
From: Jos v. d. O. <jos...@wu...> - 2003-04-17 13:53:21
|
I'm trying to debug an OpenGL program on a Pentium IV with an NVidia Riva TNT2 graphics card. However valgrind from today's CVS on SuSE 8.2 gives me this error: disInstr: unhandled 2-byte opcode: 0x28 0x2 0xF This _might_ be the result of executing a SSE, SSE2 or 3DNow! instruction. Valgrind does not currently support such instructions. Sorry. Aborted Now I'm rather clueless about SSE, but I know 3DNow is Athlon specific. Is SSE Pentium related? Or is MMX not completely implemented yet? Best regards, Jos van den Oever |
|
From: Mathieu M. <Mat...@cr...> - 2003-04-17 14:09:10
|
If you are using the lastest nvidia driver you can use: $__GL_FORCE_GENERIC_CPU=1 valgrind ... mathieu Jos van den Oever wrote: > I'm trying to debug an OpenGL program on a Pentium IV with an NVidia > Riva TNT2 graphics card. However valgrind from today's CVS on SuSE 8.2 > gives me this error: > > disInstr: unhandled 2-byte opcode: 0x28 0x2 0xF > This _might_ be the result of executing a SSE, SSE2 or 3DNow! > instruction. Valgrind does not currently support such instructions. > Sorry. > Aborted > > Now I'm rather clueless about SSE, but I know 3DNow is Athlon specific. > Is SSE Pentium related? Or is MMX not completely implemented yet? > > Best regards, Jos van den Oever > > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > _______________________________________________ > Valgrind-users mailing list > Val...@li... > https://lists.sourceforge.net/lists/listinfo/valgrind-users > -- Mathieu Malaterre CREATIS 28 Avenue du Doyen LEPINE B.P. Lyon-Montchat 69394 Lyon Cedex 03 http://www.creatis.insa-lyon.fr/~malaterre/ |
|
From: Melchior F. <mf...@us...> - 2003-04-17 14:18:32
|
* Mathieu Malaterre -- Thursday 17 April 2003 16:03: > If you are using the lastest nvidia driver you can use: > > $__GL_FORCE_GENERIC_CPU=1 valgrind ... Or else you can still override the nvidia driver by mesa, as in $ LD_PRELOAD=/usr/lib/GL/libGL.so.1.3.mesasoft valgrind ... m. |
|
From: Jos v. d. O. <jos...@wu...> - 2003-04-23 09:49:17
|
Thanks Mathieu, Melchior and Melchior, I've succesfully found the memory leak by using the software mesa library instead of the nvidida driver. Best regards, Jos Melchior FRANZ wrote: > * Mathieu Malaterre -- Thursday 17 April 2003 16:03: > >>If you are using the lastest nvidia driver you can use: >> >>$__GL_FORCE_GENERIC_CPU=1 valgrind ... > > > Or else you can still override the nvidia driver by mesa, as in > > $ LD_PRELOAD=/usr/lib/GL/libGL.so.1.3.mesasoft valgrind ... > > m. > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > _______________________________________________ > Valgrind-users mailing list > Val...@li... > https://lists.sourceforge.net/lists/listinfo/valgrind-users |
|
From: Nicholas N. <nj...@ca...> - 2003-04-17 14:12:16
|
On Thu, 17 Apr 2003, Jos van den Oever wrote:
> Now I'm rather clueless about SSE, but I know 3DNow is Athlon specific.
> Is SSE Pentium related? Or is MMX not completely implemented yet?
SSE and SSE2 are yet more sets of extra instructions, like MMX and 3DNow.
They are supported by modern Pentiums and Athlons. Valgrind doesn't yet
support them.
However, NVidia also noticed this it seems, and the "latest" drivers
(version 4349, apparently) come with this text
DISABLING CPU SPECIFIC FEATURES
Setting the environment variable __GL_FORCE_GENERIC_CPU to a
non-zero value will inhibit the use of CPU specific features
such as MMX, SSE, or 3DNOW!. Use of this option may result in
performance loss. This option may be useful in conjunction with
software such as the Valgrind memory debugger.
Set __GL_FORCE_GENERIC_CPU=1 and Valgrind should work.
N
|
|
From: Todd R. <ric...@pr...> - 2003-04-17 18:00:09
|
I just started using valgrind and it has already found 2 nasty buffer
overruns for me. However, it only works on my single threaded programs. I
have a MT server that uses a thread pool for incoming socket requests - one
thread poll()s on all fds and then queues up work objects to be run by slave
threads. My problem is that once the master thread is started, it runs
properly in a poll() loop (with a few second timeout), but other threads
receive almost no cpu time, including the original main thread that started
the master poller! At first I thought all other threads were hung
indefinitely, but I left the program run for 30+ minutes and the main thread
finally printed out a debug string after the pthread_create() so slowly that
it did so one character at a time over several minutes.
I am using Redhat 8 updated to all current patches which includes glibc
2.3.2 and have tried both vgrind 1.9.5 and the 2.0 cvs branch
Thanks,
Todd
|
|
From: Julian S. <js...@ac...> - 2003-04-17 23:32:38
|
That's very strange. V has threading problems with glibcs > 2.3.1, though. So I wonder if that's it. Do you have an older linux distro you can try it on, something like RH 7.3, or Suse 8.1 ? Basically anything with glibc 2.3.1 or before; 2.2.5 would be even better. J On Thursday 17 April 2003 6:58 pm, Todd Richmond wrote: > I just started using valgrind and it has already found 2 nasty buffer > overruns for me. However, it only works on my single threaded programs. I > have a MT server that uses a thread pool for incoming socket requests - one > thread poll()s on all fds and then queues up work objects to be run by > slave threads. My problem is that once the master thread is started, it > runs properly in a poll() loop (with a few second timeout), but other > threads receive almost no cpu time, including the original main thread that > started the master poller! At first I thought all other threads were hung > indefinitely, but I left the program run for 30+ minutes and the main > thread finally printed out a debug string after the pthread_create() so > slowly that it did so one character at a time over several minutes. > > I am using Redhat 8 updated to all current patches which includes glibc > 2.3.2 and have tried both vgrind 1.9.5 and the 2.0 cvs branch > > Thanks, > Todd > > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > _______________________________________________ > Valgrind-users mailing list > Val...@li... > https://lists.sourceforge.net/lists/listinfo/valgrind-users |