public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: sdouglass@arm.com To: gcc-gnats@gcc.gnu.org Cc: swallis@arm.com Subject: c/7733: Segmentation Fault with -ftest-coverage Date: Tue, 27 Aug 2002 05:36:00 -0000 [thread overview] Message-ID: <20020827121226.21894.qmail@sources.redhat.com> (raw) >Number: 7733 >Category: c >Synopsis: Segmentation Fault with -ftest-coverage >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Tue Aug 27 05:16:00 PDT 2002 >Closed-Date: >Last-Modified: >Originator: sdouglass@arm.com >Release: gcc 3.1 >Organization: >Environment: SunOS 5.6 ../src-solaris_2_6-sparc/configure --prefix=/arm/sdt/tools/GNU/gcc/3_1 --exec-prefix=/arm/sdt/tools/GNU/gcc/3_1/solaris_2_6-sparc --program-suffix=-3_1 -v --with-dwarf2 --enable-version-specific-runtime-libs --with-gnu-as --with-as=/arm/sdt/tools/GNU/binutils/2_12/solaris_2_6-sparc/bin/as-2_12 --with-gnu-ld --with-ld=/arm/sdt/tools/GNU/binutils/2_12/solaris_2_6-sparc/bin/ld-2_12 >Description: Compiling this with '-ftest-coverage -c' on SunOS/Solaris 5.6 causes: longjmp.c:5: internal error: Segmentation Fault #include <setjmp.h> static jmp_buf buf; void f(int i) { longjmp(buf, i); } >How-To-Repeat: gcc -ftest-coverage -c longjmp.c Here's the .i file (after preprocessing): # 1 "longjmp.c" # 1 "<built-in>" # 1 "<command line>" # 1 "longjmp.c" # 1 "/usr/include/setjmp.h" 1 3 4 # 17 "/usr/include/setjmp.h" 3 4 #pragma ident "@(#)setjmp.h 1.26 96/12/18 SMI" # 1 "/usr/include/sys/feature_tests.h" 1 3 4 # 11 "/usr/include/sys/feature_tests.h" 3 4 #pragma ident "@(#)feature_tests.h 1.13 97/06/26 SMI" # 20 "/usr/include/setjmp.h" 2 3 4 # 53 "/usr/include/setjmp.h" 3 4 typedef int jmp_buf[12]; extern int setjmp(jmp_buf); #pragma unknown_control_flow(setjmp) extern int _setjmp(jmp_buf); #pragma unknown_control_flow(_setjmp) extern void longjmp(jmp_buf, int); extern void _longjmp(jmp_buf, int); typedef int sigjmp_buf[19]; extern int sigsetjmp(sigjmp_buf, int); #pragma unknown_control_flow(sigsetjmp) extern void siglongjmp(sigjmp_buf, int); # 2 "longjmp.c" 2 static jmp_buf buf; void f(int i) { longjmp(buf, i); } >Fix: >Release-Note: >Audit-Trail: >Unformatted:
next reply other threads:[~2002-08-27 12:16 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-08-27 5:36 sdouglass [this message] 2002-08-27 9:26 nathan 2003-05-10 4:16 Dara Hazeghi 2003-05-10 7:46 giovannibajo 2003-05-13 9:36 Simon Wallis 2003-05-16 18:36 Dara Hazeghi
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=20020827121226.21894.qmail@sources.redhat.com \ --to=sdouglass@arm.com \ --cc=gcc-gnats@gcc.gnu.org \ --cc=swallis@arm.com \ /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).