public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: bug-in-gcc@kivc.vstu.vinnica.ua To: gcc-gnats@gcc.gnu.org Subject: preprocessor/2654: Bug with miltiple args. #DEFINE - causes cpp to SIGSEGV Date: Thu, 26 Apr 2001 05:16:00 -0000 [thread overview] Message-ID: <20010426121434.31021.qmail@sourceware.cygnus.com> (raw) >Number: 2654 >Category: preprocessor >Synopsis: Bug with miltiple args. #DEFINE - causes cpp to SIGSEGV >Confidential: no >Severity: critical >Priority: medium >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Thu Apr 26 05:16:00 PDT 2001 >Closed-Date: >Last-Modified: >Originator: Bohdan Vlasyuk (myself) >Release: gcc version 2.95.2 19991024 (release) >Organization: >Environment: Linux rh-clone (Black Cat, versions don't differ) 6.2 $ rpm -qa|grep egcs egcs-1.1.2-30 egcs-c++-1.1.2-30 $ uname -a Linux kivc.vstu.vinnica.ua 2.2.18 #9 Wed Feb 14 13:38:20 EET 2001 i686 unknown >Description: Hi !!! What I am doing is $ gcc test.cpp gcc: Internal compiler error: program cpp got fatal signal 11 $ gcc -v Reading specs from /usr/local/lib/gcc-lib/i686-pc-linux-gnu/2.95.2/specs gcc version 2.95.2 19991024 (release) The actual file test.cpp is: #define DEB(y,x...) fprintf(stderr, #x" = "#y"\n",x) void main(void) { int fromblock; DEB(toblock) } Well, I know that the problem is with wrong args. number to the macro I define, however, SIGSEGV is a strange way to report errors, isn't it ?? WBR, Bohdan. >How-To-Repeat: #define DEB(y,x...) fprintf(stderr, #x" = "#y"\n",x) void main(void) { int fromblock; DEB(toblock) } >Fix: >Release-Note: >Audit-Trail: >Unformatted:
reply other threads:[~2001-04-26 5:16 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20010426121434.31021.qmail@sourceware.cygnus.com \ --to=bug-in-gcc@kivc.vstu.vinnica.ua \ --cc=gcc-gnats@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).