vs-svn11716 fc6 86_64 make output

[wirser]

hardly enough warnings to complain about

src/cmd/unit_generic.cpp: In member function ‘bool Unit::UpAndDownGrade(const Unit*, const Unit*, int, int, bool, bool, int, bool, double&, const Unit*, bool, bool)’:
src/cmd/unit_generic.cpp:7718: warning: converting to ‘unsigned char’ from ‘double’
src/cmd/unit_generic.cpp:7728: warning: converting to ‘int’ from ‘double’
src/cmd/unit_generic.cpp:7880: warning: converting to ‘char’ from ‘double’
src/cmd/unit_generic.cpp:7895: warning: converting to ‘char’ from ‘double’
In file included from src/cmd/collide/prapid.cpp:68:
src/cmd/collide/garray.h:142:1: warning: "CS_DECLARE_GROWING_ARRAY_REF" redefined
In file included from src/cmd/collide/prapid.cpp:63:
src/cmd/collide/cs_compat.h:80:1: warning: this is the location of the previous definition
src/networking/netserver_devices.cpp: In member function ‘void NetServer::sendJump(Unit*, Unit*, std::string)’:
src/networking/netserver_devices.cpp:333: warning: converting to non-pointer type ‘int’ from NULL
./src/cmd/container.h:29: warning: inline function ‘Unit* UnitContainer::GetUnit()’ used but never defined

but then there is valgrind

this line is the last compiler line

g++ -pipe -I/usr/include/SDL -D_GNU_SOURCE=1 -D_REENTRANT -pthread -L/usr/X11R6/lib -L/usr/X11R6/lib -o vslauncher -L/lib64 -lgtk-x11-2.0 -lgdk-x11-2.0 -latk-1.0 -lgdk_pixbuf-2.0 -lm -lpangocairo-1.0 -lpango-1.0 -lcairo -lgobject-2.0 -lgmodule-2.0 -ldl -lglib-2.0 launcher/vslauncher-saveinterface.o launcher/vslauncher-general.o src/common/vslauncher-common.o -L/usr/X11R6/lib -L/usr/X11R6/lib -lvorbisfile -lvorbis -logg -lutil -L/usr/lib64 -lSDL -lpthread -lGL -lGLU -lXmu -lXi -lglut -lexpat -lpng -ljpeg -lopenal -lvorbisfile -lvorbis

"-L/usr/X11R6/lib" appears more than once not a show stopper I'm sure , it just looks bad

[wirser]

here is a laek from elohim to bernards star cargo run

[ace123]

Yeah there are a lot of memory leaks. Valgrind didn't tell you where any of them are from.

What you posted were the errors... however every one of those were Python or system libraries which have their own memory management systems.

You must use a "suppression" file to prevent Valgrind from displaying errors about those system libraries, and to get anything useful out of it... you can google for suppressing python and nvidia, etc.

The only thing that looks odd is that three python errors referenced memory freed in CSV tables, but there are so many reasons that it is probably a coincidence.