[Valgrind-users] openoffice and valgrind1.9.6 - strange problems. Using rh8.

[Dan K. <da...@ke...>]

Hi, I'm using valgrind 1.9.6 on redhat 8.0 with OpenOffice.
It seems to work fine with no options, but if I turn on
--gdb-attach=yes, I don't get what I expect.  On the
first error, it asks me nicely if I want to run gdb,
and it does start gdb, but here's what I see:

==18736== ---- Attach to GDB ? --- [Return/N/n/Y/y/C/c] ---- y
==18736== starting GDB with cmd: /usr/bin/gdb -nw /proc/18736/exe 18736
GNU gdb Red Hat Linux (5.2.1-4)
Copyright 2002 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 "i386-redhat-linux"...
(no debugging symbols found)...
Attaching to program: /opt/OpenOffice.org644/program/soffice.bin, process 18736
Reading symbols from /usr/local/lib/valgrind/vgskin_memcheck.so...done.
Loaded symbols for /usr/local/lib/valgrind/vgskin_memcheck.so
Reading symbols from /usr/local/lib/valgrind/valgrind.so...done.
Loaded symbols for /usr/local/lib/valgrind/valgrind.so
Reading symbols from /opt/OpenOffice.org644/program/libvcl644li.so...done.
Loaded symbols for /opt/OpenOffice.org644/program/libvcl644li.so
... etc etc ...
Reading symbols from /opt/OpenOffice.org644/program/libsal.so.3...done.
Loaded symbols for /opt/OpenOffice.org644/program/libsal.so.3
Reading symbols from /usr/X11R6/lib/libXext.so.6...done.
Loaded symbols for /usr/X11R6/lib/libXext.so.6

[1]+  Stopped                 ./soffice-valgrind.sh

If I then do a fg, it seems to continue, but things are all screwed up.
gdb goes away as soon as it finishes loading up:

vg_do_syscall3 (syscallno=4294966784, arg1=18738, arg2=0, arg3=0)
     at vg_mylibc.c:92
92      }
(gdb) ==18736==
==18736== GDB has detached.  Valgrind regains control.  We continue.

and the app continues on, seemingly in the background, while I'm
dumped back to the shell.  Very odd.

Any suggestions?

Thanks,
Dan

-- 
Dan Kegel
http://www.kegel.com
http://counter.li.org/cgi-bin/runscript/display-person.cgi?user=78045