public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: ark@research.att.com
To: gcc-gnats@gcc.gnu.org
Subject: target/3427: g++3.0 produces executables that don't work at all on Solaris 2.6
Date: Tue, 26 Jun 2001 10:06:00 -0000	[thread overview]
Message-ID: <200106261704.NAA07483@europa.research.att.com> (raw)

>Number:         3427
>Category:       target
>Synopsis:       g++3.0 produces executables that don't work at all on Solaris 2.6
>Confidential:   no
>Severity:       critical
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Tue Jun 26 10:06:01 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator:     Andrew Koenig
>Release:        3.0
>Organization:
AT&T Research, Florham Park, NJ
>Environment:
System: SunOS europa 5.6 Generic_105181-05 sun4u sparc SUNW,Ultra-5_10
Architecture: sun4

	
host: sparc-sun-solaris2.6
build: sparc-sun-solaris2.6
target: sparc-sun-solaris2.6
configured with: /tmp/build-gnu21809/gcc-3.0/configure --prefix=/usr/gnu --with-ld=/usr/gnu/bin/ld --with-as=/usr/gnu/bin/as --with-gnu-ld --with-gnu-as
>Description:
	When I compile even a trivial program under Solaris 2.6,
	the resulting executable crashes.
>How-To-Repeat:
	When I compile the following program:

	int main()
	{
		return 0;
	}

	I get an executable that dumps core:

	[europa] LD_LIBRARY_PATH=/usr/gnu/lib a.out
	Segmentation Fault - core dumped

	Here is what gdb says about it on my system:

	[europa] gdb a.out core
	GNU gdb 5.0
	Copyright 2000 Free Software Foundation, Inc.
	GDB is free software, covered by the GNU General Public License, and you are
	welcome to change it and/or distribute copies of it under certain conditions.
	Type "show copying" to see the conditions.
	There is absolutely no warranty for GDB.  Type "show warranty" for details.
	This GDB was configured as "sparc-sun-solaris2.6"...(no debugging symbols found)...
	Core was generated by `a.out'.
	Program terminated with signal 11, Segmentation Fault.
	Reading symbols from /usr/gnu/lib/libstdc++.so.3...done.
	Loaded symbols for /usr/gnu/lib/libstdc++.so.3
	Reading symbols from /usr/lib/libm.so.1...done.
	Loaded symbols for /usr/lib/libm.so.1
	Reading symbols from /usr/gnu/lib/libgcc_s.so.1...done.
	Loaded symbols for /usr/gnu/lib/libgcc_s.so.1
	Reading symbols from /usr/lib/libc.so.1...done.
	Loaded symbols for /usr/lib/libc.so.1
	Reading symbols from /usr/lib/libdl.so.1...done.
	Loaded symbols for /usr/lib/libdl.so.1
	Reading symbols from /usr/platform/SUNW,Ultra-5_10/lib/libc_psr.so.1...done.
	Loaded symbols for /usr/platform/SUNW,Ultra-5_10/lib/libc_psr.so.1
	#0  0xef757b84 in __do_global_dtors_aux () from /usr/gnu/lib/libstdc++.so.3
	(gdb) bt
	#0  0xef757b84 in __do_global_dtors_aux () from /usr/gnu/lib/libstdc++.so.3
	#1  0xef784640 in _fini () from /usr/gnu/lib/libstdc++.so.3
	#2  0xef7d96c0 in ?? ()
	#3  0xef618d30 in _exithandle () from /usr/lib/libc.so.1
	#4  0xef6874b8 in exit () from /usr/lib/libc.so.1

	I am using bintools 2.11.2 (compiled under g++ 2.95.3) and I have
	successfully rebuilt gcc 3.0 from scratch using gcc 3.0

>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:


             reply	other threads:[~2001-06-26 10:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-26 10:06 ark [this message]
2001-11-13  8:14 rodrigc
2001-11-13  8:19 rodrigc

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=200106261704.NAA07483@europa.research.att.com \
    --to=ark@research.att.com \
    --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: 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).