[Valgrind-users] valgrind not working with gdb

[Thiago I. <iz...@ya...>]

Hi I'm using valgrind-3.4.0.SVN (I've noticed this with older versions as well) and gdb 6.5 on 64bit linux. When I attach gdb to my program running under valgrind the following occurs:

==15529== Conditional jump or move depends on uninitialised value(s)
==15529==    at 0x55A093C: Manta::DynBVH::firstIntersects(Manta::BBox const&, Manta::RayPacket const&, Manta::DynBVH::IAData const&, float*) const (DynBVH.cc:238)
==15529==    by 0x55A0D33: Manta::DynBVH::intersectNode(int, Manta::RenderContext const&, Manta::RayPacket&, Manta::DynBVH::IAData const&) const (DynBVH.cc:82)
==15529==    by 0x55A0DB6: Manta::DynBVH::intersectNode(int, Manta::RenderContext const&, Manta::RayPacket&, Manta::DynBVH::IAData const&) const (DynBVH.cc:114)
==15529==    by 0x55A1306: Manta::DynBVH::intersect(Manta::RenderContext const&, Manta::RayPacket&) const (DynBVH.cc:74)
==15529==    by 0x55AEA8E: Manta::Group::intersect(Manta::RenderContext const&, Manta::RayPacket&) const (Group.cc:211)
==15529==    by 0x52E7E8D: Manta::HardShadows::computeShadows(Manta::RenderContext const&, Manta::ShadowAlgorithm::StateBuffer&, Manta::LightSet const*, Manta::RayPacket&, Manta::RayPacket&) (HardShadows.cc:324)
==15529==    by 0x55FD88A: Manta::Lambertian::shade(Manta::RenderContext const&, Manta::RayPacket&) const (Lambertian.cc:95)
==15529==    by 0x52E61FE: Manta::Raytracer::traceRays(Manta::RenderContext const&, Manta::RayPacket&) (Raytracer.cc:76)
==15529==    by 0x52D3CDF: Manta::SingleSampler::renderFragment(Manta::RenderContext const&, Manta::Fragment&) (SingleSampler.cc:168)
==15529==    by 0x52C7554: Manta::TiledImageTraverser::renderImage(Manta::RenderContext const&, Manta::Image*) (TiledImageTraverser.cc:204)
==15529==    by 0x52A0810: Manta::RTRT::internalRenderLoop(int, bool) (RTRT.cc:935)
==15529==    by 0x52A2254: Manta::RTRT::beginRendering(bool) (RTRT.cc:523)
==15529==    by 0x413605: main (manta.cc:497)
==15529== 
==15529== ---- Attach to debugger ? --- [Return/N/n/Y/y/C/c] ---- y
==15529== starting debugger with cmd: /usr/bin/gdb -nw /proc/15531/fd/1024 15531
GNU gdb 6.5
Copyright (C) 2006 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "x86_64-suse-linux"...Using host libthread_db library "/lib64/libthread_db.so.1".

Attaching to program: /proc/15531/fd/1024, process 15531
0x00000000055a093c in ?? ()
(gdb) where
#0  0x00000000055a093c in ?? ()
#1  0x00000007feff1380 in ?? ()
#2  0x00000000055a0d34 in ?? ()
#3  0x303600000063c588 in ?? ()
#4  0x0000000007668d88 in ?? ()
#5  0x0000000000000028 in ?? ()
#6  0x0000000000003800 in ?? ()
#7  0x2000000000000000 in ?? ()
#8  0x00000000078ce440 in ?? ()
#9  0x00000000078ccc10 in ?? ()
#10 0x0000000000000000 in ?? ()

I clearly have debugging symbols since valgrind can find them and if I run gdb directly on my program everything also works fine. What should I do to be able to debug my code with gdb?

Thanks,
Thiago




      ____________________________________________________________________________________
Be a better friend, newshound, and 
know-it-all with Yahoo! Mobile.  Try it now.  http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ