[Valgrind-users] Segment override again ?

[<yu...@ii...>]

I'm running on a Linux 2.5.70 Hyperthreading-aware P4 machine with the latest 
nvidia drivers and latest KDE cvs.  Should valgrind work with this setup? I 
know it worked with my older PIII/nvidia system a few weeks ago.  When I try 
'valgrind kwrite' I get

==693== Memcheck, a.k.a. Valgrind, a memory error detector for x86-linux.
==693== Copyright (C) 2002-2003, and GNU GPL'd, by Julian Seward.
==693== Using valgrind-cvs-head-2003-04-23, a program supervision framework 
for x86-linux.
==693== Copyright (C) 2000-2003, and GNU GPL'd, by Julian Seward.
==693== Estimated CPU clock rate is 3087 MHz
==693== For more details, rerun with: -v
==693==
==693==
==693== Valgrind detected that your program requires
==693== the following unimplemented functionality:
==693==    x86 segment override (SEG=CS) prefix
==693== This may be because the functionality is hard to implement,
==693== or because no reasonable program would behave this way,
==693== or because nobody has yet needed it.  In any case, let me know
==693== (js...@ac...) and/or try to work around the problem, if you can.
==693==
==693== Valgrind has to exit now.  Sorry.  Bye!
==693==

sched status:

Thread 1: status = Runnable, associated_mx = 0x0, associated_cv = 0x0
==693==    at 0x4000ABC9: call_init (in /lib/ld-2.3.2.so)
==693==    by 0x4000ADBE: _dl_init_internal (in /lib/ld-2.3.2.so)
==693==    by 0x400009EC: (within /lib/ld-2.3.2.so)

-Jesse