public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Matthias Klose <doko@net.local> To: gcc-gnats@gcc.gnu.org, debian-gcc@lists.debian.org Subject: c++/10427: [3.0/3.2/3.3/3.4 regression] Stack corruption with variable-length automatic arrays and virtual destructors Date: Thu, 17 Apr 2003 20:06:00 -0000 [thread overview] Message-ID: <E196FXy-0000KI-00@tango.net.local> (raw) >Number: 10427 >Category: c++ >Synopsis: [3.0/3.2/3.3/3.4 regression] Stack corruption with variable-length automatic arrays and virtual destructors >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: wrong-code >Submitter-Id: net >Arrival-Date: Thu Apr 17 20:06:00 UTC 2003 >Closed-Date: >Last-Modified: >Originator: Toni Timonen <ttimonen@users.sourceforge.net> >Release: >Organization: The Debian Project >Environment: >Description: [ Reported to the Debian BTS as report #188527. Please CC 188527@bugs.debian.org on replies. Log of report can be found at http://bugs.debian.org/188527 ] Regression from 2.95, rechecked with 3.0.4, 3.2 20030415, 3.3 20030415, HEAD 20030329. the following program compiles (compiled as "g++ stackcorrupt.cpp"), but crashes when run. It seems that the stack gets corrupted with that variable-length array when A class with a virtual function is used and the length assigning variable(foo) is being changed. stackcorrupt.cpp: --snip-- class A { public: virtual ~A() {} }; int main(void) { int foo=1; A bar[foo]; foo++; return 0; } --snip-- The same problem can also be reproduced by using the compiler from the gcc-snapshot (20030314-1) or with the g++-3.0 (3.0.4-13). The g++-2.95 (2.95.4-17) does not have the same problem. >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted:
reply other threads:[~2003-04-17 20:06 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=E196FXy-0000KI-00@tango.net.local \ --to=doko@net.local \ --cc=188527@bugs.debian.org \ --cc=debian-gcc@lists.debian.org \ --cc=gcc-gnats@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).