public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: "Gerwin, Joshua A" <joshua.a.gerwin@intel.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: RE: preprocessor/6084: cpp Segmentation Fault
Date: Wed, 03 Apr 2002 17:06:00 -0000	[thread overview]
Message-ID: <20020404010601.11120.qmail@sources.redhat.com> (raw)

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

From: "Gerwin, Joshua A" <joshua.a.gerwin@intel.com>
To: "'Neil Booth'" <neil@daikokuya.demon.co.uk>
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: Wed, 3 Apr 2002 16:57:40 -0800 

 I bit the bullet, built gdb on the 64-bit solaris 2.7 platform, and here's
 what I see:
 
 (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 ()
 (gdb) 
 
 > -----Original Message-----
 > From: Neil Booth [mailto:neil@daikokuya.demon.co.uk]
 > Sent: Tuesday, April 02, 2002 10:26 PM
 > To: Gerwin, Joshua A
 > Cc: 'neil@gcc.gnu.org'; 'gcc-bugs@gcc.gnu.org'; 'joshg@hf.intel.com';
 > 'rnesius@ichips.intel.com'; Nguyen, Tuan; 'gcc-gnats@gcc.gnu.org'
 > Subject: Re: preprocessor/6084: cpp Segmentation Fault
 > 
 > 
 > So, do you have a backtrace?  All you need to do is run the program
 > cpp0 within GDB, with the command line arguments you gave, and
 > when it segfaults give the "bt" command.
 > 
 > Neil.
 > 


             reply	other threads:[~2002-04-04  1:06 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-03 17:06 Gerwin, Joshua A [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 22:36 'Neil Booth'
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=20020404010601.11120.qmail@sources.redhat.com \
    --to=joshua.a.gerwin@intel.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: 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).