public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: 'Neil Booth' <neil@daikokuya.demon.co.uk>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: preprocessor/6084: cpp Segmentation Fault
Date: Wed, 03 Apr 2002 22:36:00 -0000	[thread overview]
Message-ID: <20020404063601.32470.qmail@sources.redhat.com> (raw)

The following reply was made to PR preprocessor/6084; it has been noted by GNATS.

From: 'Neil Booth' <neil@daikokuya.demon.co.uk>
To: "Gerwin, Joshua A" <joshua.a.gerwin@intel.com>
Cc: "'neil@gcc.gnu.org'" <neil@gcc.gnu.org>,
	"'gcc-bugs@gcc.gnu.org'" <gcc-bugs@gcc.gnu.org>,
	"'joshg@hf.intel.com'" <joshg@hf.intel.com>,
	"'rnesius@ichips.intel.com'" <rnesius@ichips.intel.com>,
	"Nguyen, Tuan" <tuan.nguyen@intel.com>,
	"'gcc-gnats@gcc.gnu.org'" <gcc-gnats@gcc.gnu.org>
Subject: Re: preprocessor/6084: cpp Segmentation Fault
Date: Thu, 4 Apr 2002 07:27:00 +0100

 Gerwin, Joshua A wrote:-
 
 > (gdb) run -dM -dD ../accessories/hello.c
 > Starting program:
 > /(path/to)/gcc/3.0.3-64/lib/gcc-lib/sparcv9-sun-solaris2/3.0.3/cpp0 -dM -dD
 > ../accessories/hello.c
 > 
 > Program received signal SIGSEGV, Segmentation fault.
 > 0xffffffff7f44035c in strlen () from /usr/lib/64/libc.so.1
 > (gdb) bt
 > #0  0xffffffff7f44035c in strlen () from /usr/lib/64/libc.so.1
 > #1  0xffffffff7f48d6d4 in _doprnt () from /usr/lib/64/libc.so.1
 > #2  0xffffffff7f48f180 in fprintf () from /usr/lib/64/libc.so.1
 > #3  0x100003d28 in maybe_print_line ()
 > #4  0x100003e1c in cb_define ()
 > #5  0x100004904 in do_define ()
 > #6  0x100004778 in run_directive ()
 > #7  0x100011d20 in init_builtins ()
 > #8  0x100012344 in cpp_start_read ()
 > #9  0x100003680 in do_preprocessing ()
 > #10 0x10000349c in main ()
 
 That's curious, because there is no fprintf in my version of 3.0.3
 in maybe_print_line.  Have you patched yours from stock 3.0.3?
 
 Could you do some more research - I have no clue from the above
 backtrace.  Maybe step in yourself and see what's going wrong?
 
 Neil.


             reply	other threads:[~2002-04-04  6:36 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-03 22:36 'Neil Booth' [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-05-21 13:34 neil
2002-05-21 13:33 neil
2002-04-17 23:52 neil
2002-04-15 19:46 Gerwin, Joshua A
2002-04-15 18:06 Richard Henderson
2002-04-15 12:06 'Neil Booth'
2002-04-15 11:36 Gerwin, Joshua A
2002-04-15 11:16 'Neil Booth'
2002-04-15 11:06 Gerwin, Joshua A
2002-04-13  1:26 Phil Edwards
2002-04-13  1:16 Phil Edwards
2002-04-12 22:16 Neil Booth
2002-04-12 16:06 Gerwin, Joshua A
2002-04-12 13:36 Phil Edwards
2002-04-03 17:06 Gerwin, Joshua A
2002-04-02 22:36 Neil Booth
2002-03-29 12:16 Neil Booth
2002-03-29 11:36 Gerwin, Joshua A
2002-03-29  0:20 neil

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=20020404063601.32470.qmail@sources.redhat.com \
    --to=neil@daikokuya.demon.co.uk \
    --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: link
Be 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).