public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Simon Wallis <simon.wallis@arm.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: c/7733: Segmentation Fault with -ftest-coverage Date: Tue, 13 May 2003 09:36:00 -0000 [thread overview] Message-ID: <20030513093601.14596.qmail@sources.redhat.com> (raw) The following reply was made to PR c/7733; it has been noted by GNATS. From: Simon Wallis <simon.wallis@arm.com> To: dhazeghi@yahoo.com Cc: gcc-gnats@gcc.gnu.org, swallis@arm.com, sdouglass@arm.com Subject: Re: c/7733: Segmentation Fault with -ftest-coverage Date: Tue, 13 May 2003 10:33:04 BST Hi Dara, I have tried compiling my application with "-fprofile-arcs -ftest-coverage -O1 -g" using gcc 3.2.3 on solaris 2.8. I no longer see the segfault during compilation. However, the resulting image always crashes very soon after start up, as follows: Program received signal SIGILL, Illegal instruction. 0x0020592c in atexit@@SYSVABI_1.3 () I have not investigated further. Simon. > Date: Fri, 9 May 2003 21:09:45 -0700 > Subject: Re: c/7733: Segmentation Fault with -ftest-coverage > From: Dara Hazeghi <dhazeghi@yahoo.com> > To: gcc-gnats@gcc.gnu.org, swallis@arm.com, sdouglass@arm.com > > http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit- > trail&database=gcc&pr=7733 > > Hello, > > using gcc 3.2.3, 3.3 branch or mainline (20030509), and compiling the > testcase with -ftest-coverage, I do not get any ICE or segfault. Can > the submitter confirm whether they are still encountering this bug with > a current gcc version? > > Dara -- Simon Wallis Senior Software Engineer, Development Systems ARM Ltd 110 Fulbourn Road Cambridge, CB1 9NJ United Kingdom Tel: +44 1223 400400, Fax: +44 1223 400410 Direct Dial: +44 1223 400429 This e-mail message is intended for the addressee(s) only and may contain information that is the property of, and/or subject to a confidentiality agreement between the intended recipient(s), their organisation and/or the ARM Group of Companies. If you are not an intended recipient of this e-mail message, you should not read, copy, forward or otherwise distribute or further disclose the information in it; misuse of the contents of this e-mail message may violate various laws in your state, country or juris diction. If you have received this e-mail message in error, please contact the originator of this e-mail message via e-mail and delete all copies of this message from your computer or network, thank you.
next reply other threads:[~2003-05-13 9:36 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-05-13 9:36 Simon Wallis [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-05-16 18:36 Dara Hazeghi 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=20030513093601.14596.qmail@sources.redhat.com \ --to=simon.wallis@arm.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).