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

[Julian S. <js...@ac...>]

Hi.  First off, I think OpenOffice is an important project
and am pleased to hear someone is valgrinding it.  OO is my
biggest, most hairy test case.  If it's possible, I'd like to
help the OOo developers be in the position where they routinely
valgrindify OOo, in the same way that the KDE and Gnome folks 
use it routinely.

I don't a RH8 box to repro this on.  But I have just tried
gdb attach/detach on SuSE 8.2 on the OOo 1.0.2 they supply,
and that works fine using the valgrind cvs head.  I did it a
bit different from you, perhaps:

   LD_LIBRARY_PATH=/opt/OpenOffice.org/program    \
   ./Inst/bin/valgrind -v -v --skin=addrcheck     \
   --gdb-attach=yes  /opt/OpenOffice.org/program/soffice.bin

I did all that directly on the command line, no shell script
or anything.  Perhaps your shell script ./soffice-valgrind.sh
is causing a problem?  Can you try something equivalent to the
above?

I fixed a threading problem that 1.9.6 has with glibc >= 2.3.2,
which caused it to mis-handle errno, but IIRC RH8 is glibc-2.3.1
and the errno problems didn't seem to afflict it.  Nevertheless
I attach a patch which fixes the problem and you should apply
it to your 1.9.6.  It'll be rolled into 1.9.7.

Let me know the outcome of the above.

The following is a question re OO on V.  With the help of Michael
Meeks at Ximian, I did manage to build from source various cvs
branches of OO (cws_srx644_ooo11beta, in the end) and valgrinded
them.  What I noticed was that (1) the number of mallocs/frees
reported by V was surprisingly low, compared with 1.0.2, 
and (2) all the buffer-overrun errors had disappeared.  And so
I wondered if OO had moved to using some kind of internal
allocator which V cannot 'see' ?  Alternatively of course all
those bugs have been fixed.

J




On Sunday 11 May 2003 9:13 pm, Dan Kegel wrote:
> 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