public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "glisse at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/56103] New: Overwrite classes on destruction for debug Date: Fri, 25 Jan 2013 10:45:00 -0000 [thread overview] Message-ID: <bug-56103-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56103 Bug #: 56103 Summary: Overwrite classes on destruction for debug Classification: Unclassified Product: gcc Version: unknown Status: UNCONFIRMED Severity: enhancement Priority: P3 Component: libstdc++ AssignedTo: unassigned@gcc.gnu.org ReportedBy: glisse@gcc.gnu.org CC: redi@gcc.gnu.org See the discussion starting here for more details: http://gcc.gnu.org/ml/libstdc++/2013-01/msg00064.html Overwriting classes like string or vector with garbage when they are destructed can help detect uses after destruction. Note that there is a suggestion to handle it at the compiler level for all classes, instead of manually for a few classes of the standard library.
next reply other threads:[~2013-01-25 10:45 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-01-25 10:45 glisse at gcc dot gnu.org [this message] 2013-01-25 11:36 ` [Bug libstdc++/56103] " redi at gcc dot gnu.org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-56103-4@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).