Menu
▾
▴
valgrind-users
|
From: Olivier C. <oli...@fr...> - 2003-06-06 16:22:54
|
Hello, When I used valgrind (cvs head) with a programs which use the XFree-4.3.x libraries I get the following: [olivier@snoopy valgrind]$ valgrind -v xcalc ==21680== Memcheck, a.k.a. Valgrind, a memory error detector for x86-linux. ==21680== Copyright (C) 2002-2003, and GNU GPL'd, by Julian Seward. ==21680== Using valgrind-1.9.4, a program supervision framework for x86-linux. ==21680== Copyright (C) 2000-2003, and GNU GPL'd, by Julian Seward. ==21680== Startup, with flags: ==21680== --suppressions=/usr/local/lib/valgrind/default.supp ==21680== -v ==21680== Reading suppressions file: /usr/local/lib/valgrind/default.supp ==21680== Estimated CPU clock rate is 2016 MHz ==21680== ==21680== ==21680== Valgrind detected that your program requires ==21680== the following unimplemented functionality: ==21680== x86 segment override (SEG=CS) prefix ==21680== This may be because the functionality is hard to implement, ==21680== or because no reasonable program would behave this way, ==21680== or because nobody has yet needed it. In any case, let me know ==21680== (js...@ac...) and/or try to work around the problem, if you can. ==21680== ==21680== Valgrind has to exit now. Sorry. Bye! ==21680== sched status: Thread 1: status = Runnable, associated_mx = 0x0, associated_cv = 0x0 ==21680== Reading syms from /home/olivier/local/opt/X/bin/xcalc ==21680== Reading syms from /lib/ld-2.2.5.so ==21680== Reading syms from /usr/local/lib/valgrind/vgskin_memcheck.so ==21680== Reading syms from /usr/local/lib/valgrind/valgrind.so ==21680== Reading syms from /home/olivier/local/opt/X/lib/libXaw.so.7.0 ==21680== Reading syms from /home/olivier/local/opt/X/lib/libXmu.so.6.2 ==21680== Reading syms from /home/olivier/local/opt/X/lib/libXt.so.6.0 ==21680== Reading syms from /home/olivier/local/opt/X/lib/libSM.so.6.0 ==21680== Reading syms from /home/olivier/local/opt/X/lib/libICE.so.6.3 ==21680== Reading syms from /home/olivier/local/opt/X/lib/libXpm.so.4.11 ==21680== Reading syms from /home/olivier/local/opt/X/lib/libXext.so.6.4 ==21680== Reading syms from /home/olivier/local/opt/X/lib/libX11.so.6.2 ==21680== Reading syms from /lib/i686/libm-2.2.5.so ==21680== object doesn't have a symbol table ==21680== object doesn't have any debug info ==21680== Reading syms from /lib/i686/libc-2.2.5.so ==21680== object doesn't have a symbol table ==21680== object doesn't have any debug info ==21680== Reading syms from /lib/libdl-2.2.5.so ==21680== object doesn't have a symbol table ==21680== object doesn't have any debug info ==21680== at 0x4032BE6C: permalloc (in /home/olivier/local/opt/X/lib/libX11.so.6.2) ==21680== by 0x4032BFD3: ExpandQuarkTable (in /home/olivier/local/opt/X/lib/libX11.so.6.2) ==21680== by 0x4032C214: _XrmInternalStringToQuark (in /home/olivier/local/opt/X/lib/libX11.so.6.2) ==21680== by 0x4032C482: XrmPermStringToQuark (in /home/olivier/local/opt/X/lib/libX11.so.6.2) If I use the XFree-4.2.1 libs I've not this problem. Any help welcome ... Thanks a lot for valgrind, a great software! Regards, Olivier |
|
From: Joshua Moore-O. <jo...@ch...> - 2003-06-08 14:01:01
|
What system are you running? The only time I got that error was when I was running gentoo and ran the march=pentium[34] gcc flags.. Currently I have compiled my system with march=i686 =O2 pipe -fomit-frame-pointer and it works well. Josh. On June 6, 2003 12:17 pm, Olivier Chapuis wrote: > Hello, > > When I used valgrind (cvs head) with a programs which use the XFree-4.3.x > libraries I get the following: > > [olivier@snoopy valgrind]$ valgrind -v xcalc > ==21680== Memcheck, a.k.a. Valgrind, a memory error detector for x86-linux. > ==21680== Copyright (C) 2002-2003, and GNU GPL'd, by Julian Seward. > ==21680== Using valgrind-1.9.4, a program supervision framework for > x86-linux. ==21680== Copyright (C) 2000-2003, and GNU GPL'd, by Julian > Seward. ==21680== Startup, with flags: > ==21680== --suppressions=/usr/local/lib/valgrind/default.supp > ==21680== -v > ==21680== Reading suppressions file: /usr/local/lib/valgrind/default.supp > ==21680== Estimated CPU clock rate is 2016 MHz > ==21680== > ==21680== > ==21680== Valgrind detected that your program requires > ==21680== the following unimplemented functionality: > ==21680== x86 segment override (SEG=CS) prefix > ==21680== This may be because the functionality is hard to implement, > ==21680== or because no reasonable program would behave this way, > ==21680== or because nobody has yet needed it. In any case, let me know > ==21680== (js...@ac...) and/or try to work around the problem, if you > can. ==21680== > ==21680== Valgrind has to exit now. Sorry. Bye! > ==21680== > > sched status: > > Thread 1: status = Runnable, associated_mx = 0x0, associated_cv = 0x0 > ==21680== Reading syms from /home/olivier/local/opt/X/bin/xcalc > ==21680== Reading syms from /lib/ld-2.2.5.so > ==21680== Reading syms from /usr/local/lib/valgrind/vgskin_memcheck.so > ==21680== Reading syms from /usr/local/lib/valgrind/valgrind.so > ==21680== Reading syms from /home/olivier/local/opt/X/lib/libXaw.so.7.0 > ==21680== Reading syms from /home/olivier/local/opt/X/lib/libXmu.so.6.2 > ==21680== Reading syms from /home/olivier/local/opt/X/lib/libXt.so.6.0 > ==21680== Reading syms from /home/olivier/local/opt/X/lib/libSM.so.6.0 > ==21680== Reading syms from /home/olivier/local/opt/X/lib/libICE.so.6.3 > ==21680== Reading syms from /home/olivier/local/opt/X/lib/libXpm.so.4.11 > ==21680== Reading syms from /home/olivier/local/opt/X/lib/libXext.so.6.4 > ==21680== Reading syms from /home/olivier/local/opt/X/lib/libX11.so.6.2 > ==21680== Reading syms from /lib/i686/libm-2.2.5.so > ==21680== object doesn't have a symbol table > ==21680== object doesn't have any debug info > ==21680== Reading syms from /lib/i686/libc-2.2.5.so > ==21680== object doesn't have a symbol table > ==21680== object doesn't have any debug info > ==21680== Reading syms from /lib/libdl-2.2.5.so > ==21680== object doesn't have a symbol table > ==21680== object doesn't have any debug info > ==21680== at 0x4032BE6C: permalloc (in > /home/olivier/local/opt/X/lib/libX11.so.6.2) ==21680== by 0x4032BFD3: > ExpandQuarkTable (in /home/olivier/local/opt/X/lib/libX11.so.6.2) ==21680== > by 0x4032C214: _XrmInternalStringToQuark (in > /home/olivier/local/opt/X/lib/libX11.so.6.2) ==21680== by 0x4032C482: > XrmPermStringToQuark (in /home/olivier/local/opt/X/lib/libX11.so.6.2) > > > If I use the XFree-4.2.1 libs I've not this problem. > > Any help welcome ... > > Thanks a lot for valgrind, a great software! > > Regards, Olivier > > > ------------------------------------------------------- > This SF.net email is sponsored by: Etnus, makers of TotalView, The best > thread debugger on the planet. Designed with thread debugging features > you've never dreamed of, try TotalView 6 free at www.etnus.com. > _______________________________________________ > Valgrind-users mailing list > Val...@li... > https://lists.sourceforge.net/lists/listinfo/valgrind-users |
|
From: Olivier C. <oli...@fr...> - 2003-06-09 14:27:54
|
On Sun, Jun 08, 2003 at 09:56:49AM -0400, Joshua Moore-Oliva wrote: > > What system are you running? > > The only time I got that error was when I was running gentoo and ran the > march=pentium[34] gcc flags.. > > Currently I have compiled my system with > > march=i686 =O2 pipe -fomit-frame-pointer > > and it works well. > > Josh. > Yes I compiled X with these options (as I've a pentium4): -O2 -march=pentium4 -fno-strength-reduce -pipe will try with march=i686. Thanks, Olivier |
|
From: Joshua Moore-O. <jo...@ch...> - 2003-06-09 14:37:41
|
Just a warning, but march=pentium 4 is broken in gcc. I've had everything from sound problems to floating point conversion problems due to it... If you have anything compiled with march=pentium4 I'd definately recommend downgrading to at least march=pentium3 since pentium4 has a floating point conversion bug that's really nasty. On June 9, 2003 10:30 am, Olivier Chapuis wrote: > On Sun, Jun 08, 2003 at 09:56:49AM -0400, Joshua Moore-Oliva wrote: > > What system are you running? > > > > The only time I got that error was when I was running gentoo and ran the > > march=pentium[34] gcc flags.. > > > > Currently I have compiled my system with > > > > march=i686 =O2 pipe -fomit-frame-pointer > > > > and it works well. > > > > Josh. > > Yes I compiled X with these options (as I've a pentium4): > > -O2 -march=pentium4 -fno-strength-reduce -pipe > > will try with march=i686. > > Thanks, Olivier > > > ------------------------------------------------------- > This SF.net email is sponsored by: Etnus, makers of TotalView, The best > thread debugger on the planet. Designed with thread debugging features > you've never dreamed of, try TotalView 6 free at www.etnus.com. > _______________________________________________ > Valgrind-users mailing list > Val...@li... > https://lists.sourceforge.net/lists/listinfo/valgrind-users |
|
From: Dan K. <da...@ke...> - 2003-06-09 14:56:58
|
Which version of gcc? gcc-3.3 fixes a whole bunch of pentium 4 bugs. - Dan Joshua Moore-Oliva wrote: > Just a warning, but march=pentium 4 is broken in gcc. > > I've had everything from sound problems to floating point conversion problems > due to it... If you have anything compiled with march=pentium4 I'd > definately recommend downgrading to at least march=pentium3 since pentium4 > has a floating point conversion bug that's really nasty. > > On June 9, 2003 10:30 am, Olivier Chapuis wrote: > >>On Sun, Jun 08, 2003 at 09:56:49AM -0400, Joshua Moore-Oliva wrote: >> >>>What system are you running? >>> >>>The only time I got that error was when I was running gentoo and ran the >>>march=pentium[34] gcc flags.. >>> >>>Currently I have compiled my system with >>> >>>march=i686 =O2 pipe -fomit-frame-pointer >>> >>>and it works well. >>> >>>Josh. >> >>Yes I compiled X with these options (as I've a pentium4): >> >>-O2 -march=pentium4 -fno-strength-reduce -pipe >> >>will try with march=i686. >> >>Thanks, Olivier >> >> >>------------------------------------------------------- >>This SF.net email is sponsored by: Etnus, makers of TotalView, The best >>thread debugger on the planet. Designed with thread debugging features >>you've never dreamed of, try TotalView 6 free at www.etnus.com. >>_______________________________________________ >>Valgrind-users mailing list >>Val...@li... >>https://lists.sourceforge.net/lists/listinfo/valgrind-users > > > > > ------------------------------------------------------- > This SF.net email is sponsored by: Etnus, makers of TotalView, The best > thread debugger on the planet. Designed with thread debugging features > you've never dreamed of, try TotalView 6 free at www.etnus.com. > _______________________________________________ > Valgrind-users mailing list > Val...@li... > https://lists.sourceforge.net/lists/listinfo/valgrind-users > > -- Dan Kegel http://www.kegel.com http://counter.li.org/cgi-bin/runscript/display-person.cgi?user=78045 |
|
From: Joshua Moore-O. <jo...@ch...> - 2003-06-09 15:10:33
|
Actually I think it is fixed in gcc 3.3 however I'm nto running it yet cause it's not marked stable yet :) Just thought I'd give youa heads up. On June 9, 2003 11:01 am, Dan Kegel wrote: > Which version of gcc? gcc-3.3 fixes a whole bunch of pentium 4 bugs. > - Dan > > Joshua Moore-Oliva wrote: > > Just a warning, but march=pentium 4 is broken in gcc. > > > > I've had everything from sound problems to floating point conversion > > problems due to it... If you have anything compiled with march=pentium4 > > I'd definately recommend downgrading to at least march=pentium3 since > > pentium4 has a floating point conversion bug that's really nasty. > > > > On June 9, 2003 10:30 am, Olivier Chapuis wrote: > >>On Sun, Jun 08, 2003 at 09:56:49AM -0400, Joshua Moore-Oliva wrote: > >>>What system are you running? > >>> > >>>The only time I got that error was when I was running gentoo and ran the > >>>march=pentium[34] gcc flags.. > >>> > >>>Currently I have compiled my system with > >>> > >>>march=i686 =O2 pipe -fomit-frame-pointer > >>> > >>>and it works well. > >>> > >>>Josh. > >> > >>Yes I compiled X with these options (as I've a pentium4): > >> > >>-O2 -march=pentium4 -fno-strength-reduce -pipe > >> > >>will try with march=i686. > >> > >>Thanks, Olivier > >> > >> > >>------------------------------------------------------- > >>This SF.net email is sponsored by: Etnus, makers of TotalView, The best > >>thread debugger on the planet. Designed with thread debugging features > >>you've never dreamed of, try TotalView 6 free at www.etnus.com. > >>_______________________________________________ > >>Valgrind-users mailing list > >>Val...@li... > >>https://lists.sourceforge.net/lists/listinfo/valgrind-users > > > > ------------------------------------------------------- > > This SF.net email is sponsored by: Etnus, makers of TotalView, The best > > thread debugger on the planet. Designed with thread debugging features > > you've never dreamed of, try TotalView 6 free at www.etnus.com. > > _______________________________________________ > > Valgrind-users mailing list > > Val...@li... > > https://lists.sourceforge.net/lists/listinfo/valgrind-users |
|
From: Dan K. <da...@ke...> - 2003-06-09 15:26:50
|
Yeah... worth a shot, though. Most of the gcc 3.3 problems I've seen so far are for other architectures (like sh4). - Dan Joshua Moore-Oliva wrote: > Actually I think it is fixed in gcc 3.3 however I'm nto running it yet cause > it's not marked stable yet :) > > Just thought I'd give youa heads up. > > On June 9, 2003 11:01 am, Dan Kegel wrote: > >>Which version of gcc? gcc-3.3 fixes a whole bunch of pentium 4 bugs. >>- Dan >> >>Joshua Moore-Oliva wrote: >> >>>Just a warning, but march=pentium 4 is broken in gcc. >>> >>>I've had everything from sound problems to floating point conversion >>>problems due to it... If you have anything compiled with march=pentium4 >>>I'd definately recommend downgrading to at least march=pentium3 since >>>pentium4 has a floating point conversion bug that's really nasty. >>> >>>On June 9, 2003 10:30 am, Olivier Chapuis wrote: >>> >>>>On Sun, Jun 08, 2003 at 09:56:49AM -0400, Joshua Moore-Oliva wrote: >>>> >>>>>What system are you running? >>>>> >>>>>The only time I got that error was when I was running gentoo and ran the >>>>>march=pentium[34] gcc flags.. >>>>> >>>>>Currently I have compiled my system with >>>>> >>>>>march=i686 =O2 pipe -fomit-frame-pointer >>>>> >>>>>and it works well. >>>>> >>>>>Josh. >>>> >>>>Yes I compiled X with these options (as I've a pentium4): >>>> >>>>-O2 -march=pentium4 -fno-strength-reduce -pipe >>>> >>>>will try with march=i686. >>>> >>>>Thanks, Olivier -- Dan Kegel http://www.kegel.com http://counter.li.org/cgi-bin/runscript/display-person.cgi?user=78045 |
|
From: Joshua Moore-O. <jo...@ch...> - 2003-06-09 15:28:02
|
If you are using gnetoo make sure you compile with --emptytree so that all depencies are recompiled as well... I ran into this problem with glibc and command line programs, recompiling glibc was not enough, I needed to recompile glibc AND it's dependancies. Hope to have helped you out. Josh. On June 9, 2003 11:01 am, Dan Kegel wrote: > Which version of gcc? gcc-3.3 fixes a whole bunch of pentium 4 bugs. > - Dan > > Joshua Moore-Oliva wrote: > > Just a warning, but march=pentium 4 is broken in gcc. > > > > I've had everything from sound problems to floating point conversion > > problems due to it... If you have anything compiled with march=pentium4 > > I'd definately recommend downgrading to at least march=pentium3 since > > pentium4 has a floating point conversion bug that's really nasty. > > > > On June 9, 2003 10:30 am, Olivier Chapuis wrote: > >>On Sun, Jun 08, 2003 at 09:56:49AM -0400, Joshua Moore-Oliva wrote: > >>>What system are you running? > >>> > >>>The only time I got that error was when I was running gentoo and ran the > >>>march=pentium[34] gcc flags.. > >>> > >>>Currently I have compiled my system with > >>> > >>>march=i686 =O2 pipe -fomit-frame-pointer > >>> > >>>and it works well. > >>> > >>>Josh. > >> > >>Yes I compiled X with these options (as I've a pentium4): > >> > >>-O2 -march=pentium4 -fno-strength-reduce -pipe > >> > >>will try with march=i686. > >> > >>Thanks, Olivier > >> > >> > >>------------------------------------------------------- > >>This SF.net email is sponsored by: Etnus, makers of TotalView, The best > >>thread debugger on the planet. Designed with thread debugging features > >>you've never dreamed of, try TotalView 6 free at www.etnus.com. > >>_______________________________________________ > >>Valgrind-users mailing list > >>Val...@li... > >>https://lists.sourceforge.net/lists/listinfo/valgrind-users > > > > ------------------------------------------------------- > > This SF.net email is sponsored by: Etnus, makers of TotalView, The best > > thread debugger on the planet. Designed with thread debugging features > > you've never dreamed of, try TotalView 6 free at www.etnus.com. > > _______________________________________________ > > Valgrind-users mailing list > > Val...@li... > > https://lists.sourceforge.net/lists/listinfo/valgrind-users |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X