public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dominik.strasser@onespin-solutions.com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/62305] New: throw segfaults on 64bit Cygwin Date: Fri, 29 Aug 2014 12:36:00 -0000 [thread overview] Message-ID: <bug-62305-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62305 Bug ID: 62305 Summary: throw segfaults on 64bit Cygwin Product: gcc Version: 4.8.2 Status: UNCONFIRMED Severity: critical Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: dominik.strasser@onespin-solutions.com The symptoms of this problems are quite similar to https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56747, however it is no *always* cured by compiling with -O1. I tried compiling various source files I have with -O0, then the problem vanished, but later reappeared on a different exception path. Another thing I tried was to put the function below into a separate file and trying with optimization options which did not succeed. Is the problem maybe located not in the catching function but in the cleanup regions of a the stack between the throw and the catch ? Host triple: x86_64-w64-mingw32-g++ The function catching the exception looks like this: pair<unsigned,unsigned> ExpRef::getConstRange(CompEnv& rCompEnv,const NetReg& crNetReg) const { CompEnv::BoolVarToggler noSideEffects(rCompEnv.deactivateSideEffects()); unsigned uiWidth = 0; try { uiWidth = crNetReg.width(rCompEnv); if (!usePreciseConstRange) { return pair<unsigned,unsigned>(uiWidth-1,0); } Sel::LLRes llIndex = checkRange(rCompEnv); if (!llIndex.isEmpty() && !llIndex.isPartiallyEmpty() && llIndex.isConstant()) { assert(llIndex.left() >= llIndex.right()); assert(llIndex.right() >= 0); assert(llIndex.llLeft() >= llIndex.llRight()); // width might be 0 in error case ... assert(llIndex.llLeft()+1 <= uiWidth); return pair<unsigned,unsigned>(llIndex.llLeft(),llIndex.llRight()); } } catch(...) { // do nothing } return pair<unsigned,unsigned>(uiWidth-1,0); } The crash looks like this: gdb: unknown target exception 0x20474343 at 0x7fefcc8940d Program received signal ?, Unknown signal. [Switching to Thread 4920.0x1124] 0x000007fefcc8940d in RaiseException () from C:\Windows\system32\KernelBase.dll (gdb) where #0 0x000007fefcc8940d in RaiseException () from C:\Windows\system32\KernelBase.dll #1 0x000000006144cd4d in libgcc_s_seh-1!_Unwind_RaiseException () from C:\cygwin64\home\cve\distributions\unreleased_distributions\Distr\latest\onespin360\onespin\bin\cygwin64\libgcc_s_seh-1.dll #2 0x000000006fcb76c8 in libstdc++-6!.cxa_throw () from C:\cygwin64\home\cve\distributions\unreleased_distributions\Distr\latest\onespin360\onespin\bin\cygwin64\libstdc++-6.dll Stackframe #3 is the throw location. I know that this is not very much I have here for diagnosis, so it is morea call for help on debugging this crash. Is there a way to find out which function is currently unwound ?
next reply other threads:[~2014-08-29 12:36 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-08-29 12:36 dominik.strasser@onespin-solutions.com [this message] 2014-10-28 8:50 ` [Bug c++/62305] " dominik.strasser@onespin-solutions.com
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-62305-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).