public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: "Christian Ehrhardt" <ehrhardt@mathematik.uni-ulm.de> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: other/3782: -fstats produces a segmentation fault Date: Tue, 10 Dec 2002 04:16:00 -0000 [thread overview] Message-ID: <20021210121616.17755.qmail@sources.redhat.com> (raw) The following reply was made to PR other/3782; it has been noted by GNATS. From: "Christian Ehrhardt" <ehrhardt@mathematik.uni-ulm.de> To: Sylvain Pion <Sylvain.Pion@sophia.inria.fr> Cc: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org, gcc-gnats@gcc.gnu.org, gcc-patches@gcc.gnu.org Subject: Re: other/3782: -fstats produces a segmentation fault Date: Tue, 10 Dec 2002 13:15:39 +0100 On Tue, Dec 10, 2002 at 12:16:31PM +0100, Sylvain Pion wrote: > > Does this still happen with your setup? > > Yes it does. With current mainline, I get : Thanks for the feedback. I only tried with gcc not with g++. I now can reproduce this, cc1plus segfaults even without ANY input file if -quiet and -fstats is passed. This one line patch (compiled but not bootstrap tested) fixes the ICE for me, not sure if this is the appropriate fix though. Someone please look at this and check it in if appropriate. --- gcc/timevar.c.orig Tue Dec 10 13:01:22 2002 +++ gcc/timevar.c Tue Dec 10 13:05:28 2002 @@ -404,7 +404,7 @@ timevar_accumulate (elapsed, &tv->start_time, &now); } /* Or is TIMEVAR at the top of the timer stack? */ - else if (stack->timevar == tv) + else if (stack && stack->timevar == tv) { get_time (&now); timevar_accumulate (elapsed, &start_time, &now); regards Christian -- THAT'S ALL FOLKS!
next reply other threads:[~2002-12-10 12:16 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-12-10 4:16 Christian Ehrhardt [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-12-10 3:26 Sylvain Pion 2002-12-09 11:20 ehrhardt 2001-07-23 14:56 Sylvain.Pion
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=20021210121616.17755.qmail@sources.redhat.com \ --to=ehrhardt@mathematik.uni-ulm.de \ --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).