At 13:37 04/11/2003 +0100, Lionel Ulmer wrote:
>On Tue, Nov 04, 2003 at 10:57:07AM +0000, Adam Gundy wrote:
>> that looks like an incorrect or corrupt segment selector (thread local storage).
>>
>> one possibility is that it is trying to use the GDT instead of the LDT - are y
At 23:06 03/11/2003 +0100, Lionel Ulmer wrote:
>> Trying to run valgrind on wine directx (running Unreal2 with nvidia openGL
>> drivers)
>
>I think it's best to use software GL when using Valgrind... It is reported
>to make the DRI crash and not support all syscalls needed by the NVIDIA GL
>driver
At 23:26 29/10/2003 -0500, Dimitrie O. Paun wrote:
>On October 29, 2003 08:44 am, Adam Gundy wrote:
>> A new tarball of valgrind modified to work with WINE is available from the
>> valgrind home page:
>>
>> http://developer.kde.org/~sewardj/
>> http://de
A new tarball of valgrind modified to work with WINE is available from the
valgrind home page:
http://developer.kde.org/~sewardj/
http://developer.kde.org/~sewardj/valgrind-20031012-wine.tar.bz2
this is based on the latest stable valgrind release.
use a current CVS or the latest snapshot of
