public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Dara Hazeghi <dhazeghi@yahoo.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: c/7733: Segmentation Fault with -ftest-coverage Date: Fri, 16 May 2003 18:36:00 -0000 [thread overview] Message-ID: <20030516183603.18287.qmail@sources.redhat.com> (raw) The following reply was made to PR c/7733; it has been noted by GNATS. From: Dara Hazeghi <dhazeghi@yahoo.com> To: Simon.Wallis@arm.com Cc: gcc-gnats@gcc.gnu.org Subject: Re: c/7733: Segmentation Fault with -ftest-coverage Date: Fri, 16 May 2003 11:35:47 -0700 (PDT) --- Simon Wallis <simon.wallis@arm.com> wrote: > I've built my application with "-fprofile-arcs > -ftest-coverage -O1 -g" > using gcc 3.3 on solaris 2.8 > > The behaviour is exactly the same as gcc 3.2.3: > It builds OK, but on startup, reports > Program received signal SIGILL, Illegal > instruction. > 0x00210ff0 in atexit@@SYSVABI_1.3 () > > I rebuilt with "-fprofile-arcs -O1 -g" and got the > same SIGILL crash. > > I rebuilt with "-O1 -g" and the image ran fine. Darn. Could you send a testcase that exhibits this particular problem, so we can figure out whether this a SPARC bug, or a profiling bug? Thanks, Dara P.S. If it's possible for you to check that this occurs under linux/x86 on gcc 3.3 too, that'd be great. __________________________________ Do you Yahoo!? The New Yahoo! Search - Faster. Easier. Bingo. http://search.yahoo.com
next reply other threads:[~2003-05-16 18:36 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-05-16 18:36 Dara Hazeghi [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-05-13 9:36 Simon Wallis 2003-05-10 7:46 giovannibajo 2003-05-10 4:16 Dara Hazeghi 2002-08-27 9:26 nathan 2002-08-27 5:36 sdouglass
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=20030516183603.18287.qmail@sources.redhat.com \ --to=dhazeghi@yahoo.com \ --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).