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: debug/7417: -ggdb3 causes internal error: Segmentation fault Date: Fri, 14 Mar 2003 15:46:00 -0000 [thread overview] Message-ID: <20030314154601.13766.qmail@sources.redhat.com> (raw) [-- Warning: decoded text below may be mangled, UTF-8 assumed --] [-- Attachment #1: Type: text/plain, Size: 1325 bytes --] The following reply was made to PR debug/7417; it has been noted by GNATS. From: Wolfgang Bangerth <bangerth@ticam.utexas.edu> To: gcc-gnats@gcc.gnu.org Cc: Subject: Re: debug/7417: -ggdb3 causes internal error: Segmentation fault Date: Fri, 14 Mar 2003 09:36:34 -0600 (CST) ---------- Forwarded message ---------- Date: Fri, 14 Mar 2003 09:15:59 +0200 (EET) From: Sami Farin <safarigcc@luukku.com> To: bangerth@dealii.org Subject: Re: debug/7417: -ggdb3 causes internal error: Segmentation fault bangerth@dealii.org wrote: > Synopsis: -ggdb3 causes internal error: Segmentation fault > > State-Changed-From-To: open->feedback > State-Changed-By: bangerth > State-Changed-When: Fri Mar 14 03:15:09 2003 > State-Changed-Why: > I tried to reproduce this, but don't have 3.1 around any > more and 3.2 doesn't crash. Could you possibly try whether > this is fixed with a newer version of gcc for you as well? 3.1.1, 3.2.1 and 3.2.2 do NOT crash. > Thanks > Wolfgang > > http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&p > r=7417 ............................................................ Maksuton sähköposti aina käytössä http://luukku.com Kuukausimaksuton MTV3 Internet-liittymä www.mtv3.fi/liittyma
next reply other threads:[~2003-03-14 15:46 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-03-14 15:46 Wolfgang Bangerth [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-03-14 15:36 bangerth 2003-03-14 3:15 bangerth
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=20030314154601.13766.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).