[google gcc-4_7, integration] Scribble on destructed strings to catch invalid accesses.

Jonathan Wakely jwakely.gcc@gmail.com
Fri Jan 25 00:15:00 GMT 2013


On 24 January 2013 19:03, Marc Glisse wrote:
> On Wed, 23 Jan 2013, Paul Pluzhnikov wrote:
>
>> This patch allows us to catch use of destructed strings.
>
>
> Hello,
>
> while a number of the google debug patches are just cheaper versions (that
> don't break the ABI) of what libstdc++'s debug mode provides, this
> overwriting of classes on destruction is not as obviously redundant, and I
> wonder whether something like it (done consistently for many classes) could
> go to trunk...

Thanks for pointing this out, Marc.

This does look like something that could be included in debug mode,
but probably not until we're back in Stage 1.  Please either put it in
Bugzilla (and CC me) or if you're diligent enough to remember please
email us again during Stage 1  :-)

Googlers, please include the libstdc++ list on patches to the
libstdc++ code, even if it's only to a google branch. I don't read
gcc-patches but am still interested in the changes you make to the
code on your branch.



More information about the Gcc-patches mailing list