public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Phil Edwards <phil@jaj.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: preprocessor/6084: cpp Segmentation Fault Date: Sat, 13 Apr 2002 01:26:00 -0000 [thread overview] Message-ID: <20020413082603.30527.qmail@sources.redhat.com> (raw) The following reply was made to PR preprocessor/6084; it has been noted by GNATS. From: Phil Edwards <phil@jaj.com> To: "Gerwin, Joshua A" <joshua.a.gerwin@intel.com> Cc: joshg@hf.intel.com, gcc-gnats@gcc.gnu.org, rnesius@ichips.intel.com, "Nguyen, Tuan" <tuan.nguyen@intel.com>, gcc-bugs@gcc.gnu.org, neil@daikokuya.demon.co.uk Subject: Re: preprocessor/6084: cpp Segmentation Fault Date: Sat, 13 Apr 2002 04:20:53 -0400 On Fri, Apr 12, 2002 at 03:57:12PM -0700, Gerwin, Joshua A wrote: > My hunch is that this is either a 3.0 problem, perhaps fixed in your version > of 3.1, or that the libc.so we're linking during compile is significantly > different. During compile of...? The compiler itself? If your libc.so were that broken, I'd expect much bigger breakage much earlier. > 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 Something is very weird here. I don't recall a "/usr/lib/64" directory under SPARC/Solaris 7. The 64-bit version should be /usr/lib/sparcv9/libc.so.1. Phil -- If ye love wealth greater than liberty, the tranquility of servitude greater than the animating contest for freedom, go home and leave us in peace. We seek not your counsel, nor your arms. Crouch down and lick the hand that feeds you; and may posterity forget that ye were our countrymen. - Samuel Adams
next reply other threads:[~2002-04-13 8:26 UTC|newest] Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-04-13 1:26 Phil Edwards [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: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-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=20020413082603.30527.qmail@sources.redhat.com \ --to=phil@jaj.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).