public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Bruno Haible <bruno@clisp.org>
To: gcc-gnats@gcc.gnu.org
Subject: other/6955: collect2 says "core dumped" when there is no core
Date: Fri, 07 Jun 2002 05:56:00 -0000 [thread overview]
Message-ID: <15616.43899.269735.378568@honolulu.ilog.fr> (raw)
>Number: 6955
>Category: other
>Synopsis: collect2 says "core dumped" when there is no core
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible: unassigned
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Fri Jun 07 05:56:04 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator: Bruno Haible
>Release: 3.1
>Organization:
GNU hackers
>Environment:
System: Linux linuix 2.4.18-4GB #1 Wed Mar 27 13:57:05 UTC 2002 i686 unknown
Architecture: i686
host: i686-pc-linux-gnu
build: i686-pc-linux-gnu
target: sparc64-unknown-linux-gnu
configured with: /packages2/gcc-3.1/configure --enable-shared --disable-nls --target=sparc64-linux --prefix=/cross/sparc64-linux-tools --with-local-prefix=/cross/sparc64-linux/local --with-as=/cross/sparc64-linux-tools/bin/sparc64-linux-as --with-gnu-as --with-ld=/cross/sparc64-linux-tools/bin/sparc64-linux-ld --with-gnu-ld --enable-languages=c
>Description:
When ld, called by collect2, crashes without a core dump, collect2 says
collect2: ld terminated with signal 11 [Segmentation fault], core dumped
But when I set "ulimit -c unlimited" and repeat the step, so that I
get a core dump, collect2 says merely
collect2: ld terminated with signal 11 [Segmentation fault]
>How-To-Repeat:
Give a link command line that makes ld crash. Once with "ulimit -c 0",
once with "ulimit -c unlimited".
>Fix:
In collect2.c, function collect_wait, change
status & 0200 ? "" : ", core dumped"
to
status & 0200 ? ", core dumped" : ""
>Release-Note:
>Audit-Trail:
>Unformatted:
next reply other threads:[~2002-06-07 12:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-07 5:56 Bruno Haible [this message]
2003-03-25 2:18 bangerth
2003-03-25 5:16 Kaveh R. Ghazi
2003-03-25 15:49 Wolfgang Bangerth
2003-03-25 16:56 Kaveh R. Ghazi
2003-03-25 17:06 Wolfgang Bangerth
2003-03-25 22:06 Mike Stump
2003-03-30 19:26 Kaveh R. Ghazi
2003-03-30 19:56 Mark Mitchell
2003-03-30 20:17 Gabriel Dos Reis
2003-03-31 4:09 ghazi
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=15616.43899.269735.378568@honolulu.ilog.fr \
--to=bruno@clisp.org \
--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).