valgrind "uninitialized value" for __cxa_begin_catch? (Only if -static)
Joe Buck
Joe.Buck@synopsys.COM
Thu Mar 27 00:15:00 GMT 2008
On Tue, Mar 25, 2008 at 12:01:19PM -0400, Benjamin Redelings wrote:
> Hi,
>
> I have noticed that, when I link my code statically, valgrind complains
> about every exception that is caught.
Hmm. Until recently valgrind didn't work on statically linked executables
at all. But I did duplicate your bug report (with gcc 4.2.2 on an
AMD-64 RHEL 4 machine).
I suggest that you ask the valgrind list if this is a real issue or
a glitch with valgrind. AFAIK the same code in __cxa_begin_catch is
used in both cases (static or dynamic). It might be that valgrind
doesn't know that this is exception-handling code if you link statically,
and doesn't do the right special-case handling.
More information about the Gcc
mailing list