Bug#227894: g++ exceptions thrown -> valgrind signals invalid read

[Jeremy Nimmer <jwnimmer@alum.mit.edu>]

Gunther,

[I'm not a DD; just a helping hand...]

On Thu, 2004-01-15 at 08:33, Gunther Laure wrote:
> Example code:
> ...
>   catch(...)
>   {
>     std::cout << "catched "<< &number << std::endl;
>   }
> ...

I am unable to reproduce your problem using my vanilla sid install:
g++-3.3 [3.3.3-0pre2] [g++-3.3 (GCC) 3.3.3 20040110 (prerelease) (Debian)]
valgrind [2.1.0-2]    [valgrind-2.1.0]

My valgrind reports no errors (and no suppressed errors, either).
Looking at diffs, mine is identical except for the noise (pid in
valgrind output, final performance counts and statistics), and the
output of the program: "catched 0xbffffad0".

I am a little disturbed that your output does not show the stdout
message ("catched...").  You may want to look into that first.

Is your libgcc1 package fresh (-0pre2)?  Is there anything unusual about
your setup?  LD_LIBRARY_PATH?

Thanks,
- Jeremy