public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Wolfgang Bangerth <bangerth@ticam.utexas.edu> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: c++/8047: [i386] Stack corruption with exceptions Date: Thu, 21 Nov 2002 17:52:00 -0000 [thread overview] Message-ID: <20021116003600.30109.qmail@sources.redhat.com> (raw) The following reply was made to PR c++/8047; it has been noted by GNATS. From: Wolfgang Bangerth <bangerth@ticam.utexas.edu> To: gcc-gnats@gcc.gnu.org, <gcc-bugs@gcc.gnu.org> Cc: Subject: Re: c++/8047: [i386] Stack corruption with exceptions Date: Fri, 15 Nov 2002 18:31:44 -0600 (CST) I just looked at this report. A reduced testcase is this: ----------------------------------- struct auto_ptr { auto_ptr(int) { } }; int foo() { throw 5; } int main() { label: try { auto_ptr x(foo()); } catch (...) { } goto label; } ---------------------------------- On closer examination, I believe this to be actually a stack corruption bug, because if I put a breakpoint into the loop, I can see how the stack pointer is decreased by 8 bytes in each iteration, which eventually leads to the program running out of space. Note that this behavior requires that you use -march=386, using i686 does not trigger the problem. Regards Wolfgang ------------------------------------------------------------------------- Wolfgang Bangerth email: bangerth@ticam.utexas.edu www: http://www.ticam.utexas.edu/~bangerth
next reply other threads:[~2002-11-16 0:36 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-11-21 17:52 Wolfgang Bangerth [this message] 2002-11-25 0:26 Danny Smith 2003-02-04 20:56 Colin Burgess
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=20021116003600.30109.qmail@sources.redhat.com \ --to=bangerth@ticam.utexas.edu \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@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).