Re: New tarball of valgrind for WINE available
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 you >> using WINE with NPTL? try it with NPTL disabled if you are... > >I am using Wine without NPTL support on a glibc-2.3.2 system but with a >stock 2.4 kernel. > >Wine works just fine, it's only Wine + Valgrind that fails. sorry for the long delay, very busy at the moment. can you try setting the environment variable: LD_ASSUME_KERNEL=2.2.5 before running valgrind - it really doesn't like NPTL. In theory the 'valgrind' shell script should be doing this if you have NPTL, but it may not be detecting things correctly... Seeya, Adam -- Real Programmers don't comment their code. If it was hard to write, it should be hard to read, and even harder to modify. These are all my own opinions.
Re: New tarball of valgrind for WINE available
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 >drivers. > >Anyway, I have a different issue : > >valgrind: vg_ldt.c:167 (vgPlain_do_useseg): Assertion (seg_selector & 7) == 7' failed. 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 you using WINE with NPTL? try it with NPTL disabled if you are... Seeya, Adam -- Real Programmers don't comment their code. If it was hard to write, it should be hard to read, and even harder to modify. These are all my own opinions.
Re: New tarball of valgrind for WINE available
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://developer.kde.org/~sewardj/valgrind-20031012-wine.tar.bz2 >> >> this is based on the latest stable valgrind release. > >Any chance this will be merge into mainline valgrind? that looks unlikely at the moment :-( Seeya, Adam -- Real Programmers don't comment their code. If it was hard to write, it should be hard to read, and even harder to modify. These are all my own opinions.
New tarball of valgrind for WINE available
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 WINE. Seeya, Adam -- Real Programmers don't comment their code. If it was hard to write, it should be hard to read, and even harder to modify. These are all my own opinions.
