public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: "Kaveh R. Ghazi" <ghazi@caip.rutgers.edu>
To: ghazi@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: other/6955: collect2 says "core dumped" when there is no core
Date: Tue, 25 Mar 2003 05:16:00 -0000	[thread overview]
Message-ID: <20030325031601.6731.qmail@sources.redhat.com> (raw)

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

From: "Kaveh R. Ghazi" <ghazi@caip.rutgers.edu>
To: bangerth@dealii.org, bruno@clisp.org, gcc-bugs@gcc.gnu.org,
        gcc-gnats@gcc.gnu.org, gcc-patches@gcc.gnu.org, gcc-prs@gcc.gnu.org,
        ghazi@gcc.gnu.org, nobody@gcc.gnu.org
Cc:  
Subject: Re: other/6955: collect2 says "core dumped" when there is no core
Date: Mon, 24 Mar 2003 22:15:46 -0500 (EST)

  > From: bangerth@dealii.org
  > 
  >     Kaveh, you inserted the lines in question in this PR some
  >     3.5 years ago. Would you mind to take a brief look at this
  >     report and its 1-line patch?
  > http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=6955
 
 Eh?  I don't recall filing or modifying this PR.  How did you
 determine I was responsible?
 
 Anyway, the patch (or suggested change) in there looks technically
 correct to me.  But I would instead do something like the patch below.
 
 (I'm not sure how to test it since I don't have code any handy that
 causes ld to crash.)
 
 		--Kaveh
 
 
 2003-03-24  Kaveh R. Ghazi  <ghazi@caip.rutgers.edu>
 
 	PR other/6955
 	* collect2.c (collect_wait): Use WCOREDUMP and fix output message.
 	* system.h (WCOREDUMP, WCOREFLG): Define if necessary.
 
 diff -rup orig/egcc-3.2-CVS20030323/gcc/collect2.c egcc-3.2-CVS20030323/gcc/collect2.c
 --- orig/egcc-3.2-CVS20030323/gcc/collect2.c	Fri Aug 16 16:02:01 2002
 +++ egcc-3.2-CVS20030323/gcc/collect2.c	Mon Mar 24 22:02:35 2003
 @@ -1522,7 +1522,7 @@ collect_wait (prog)
  	  int sig = WTERMSIG (status);
  	  error ("%s terminated with signal %d [%s]%s",
  		 prog, sig, strsignal(sig),
 -		 status & 0200 ? "" : ", core dumped");
 +		 WCOREDUMP(status) ? ", core dumped" : "");
  	  collect_exit (FATAL_EXIT_CODE);
  	}
  
 diff -rup orig/egcc-3.2-CVS20030323/gcc/system.h egcc-3.2-CVS20030323/gcc/system.h
 --- orig/egcc-3.2-CVS20030323/gcc/system.h	Tue May 21 19:44:39 2002
 +++ egcc-3.2-CVS20030323/gcc/system.h	Mon Mar 24 21:59:44 2003
 @@ -266,6 +266,12 @@ extern int errno;
  #ifndef WSTOPSIG
  #define WSTOPSIG WEXITSTATUS
  #endif
 +#ifndef WCOREDUMP
 +#define WCOREDUMP(S) ((S) & WCOREFLG)
 +#endif
 +#ifndef WCOREFLG
 +#define WCOREFLG 0200
 +#endif
  
  /* The HAVE_DECL_* macros are three-state, undefined, 0 or 1.  If they
     are defined to 0 then we must provide the relevant declaration


             reply	other threads:[~2003-03-25  3:16 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-25  5:16 Kaveh R. Ghazi [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-03-31  4:09 ghazi
2003-03-30 20:17 Gabriel Dos Reis
2003-03-30 19:56 Mark Mitchell
2003-03-30 19:26 Kaveh R. Ghazi
2003-03-25 22:06 Mike Stump
2003-03-25 17:06 Wolfgang Bangerth
2003-03-25 16:56 Kaveh R. Ghazi
2003-03-25 15:49 Wolfgang Bangerth
2003-03-25  2:18 bangerth
2002-06-07  5:56 Bruno Haible

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=20030325031601.6731.qmail@sources.redhat.com \
    --to=ghazi@caip.rutgers.edu \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=ghazi@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).