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: Sun, 30 Mar 2003 19:26:00 -0000	[thread overview]
Message-ID: <20030330191601.14103.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@ices.utexas.edu
Cc: bruno@clisp.org, gcc-bugs@gcc.gnu.org, gcc-gnats@gcc.gnu.org,
        gcc-patches@gcc.gnu.org, gdr@integrable-solutions.net,
        mark@codesourcery.com
Subject: Re: other/6955: collect2 says "core dumped" when there is no core
Date: Sun, 30 Mar 2003 14:07:12 -0500 (EST)

  > From: Wolfgang Bangerth <bangerth@ticam.utexas.edu>
  > 
  > Let the patch go in! (I think it qualifies as "obvious".)
  > Thanks
  >  Wolfgang
 
 Well, "obvious" patches still should be tested somehow.  I figured out
 a way.  After compiling gcc, I replaced "ld" with a shell script like
 so, alternately replacing SEGV with TERM to control whether to
 create a core from "ld".
 
  > #!/bin/bash
  > kill -SEGV $$
 
 I verified that the current compiler's error message is wrong, and the
 patch fixes it.
 
 So I went ahead and installed it on the mainline as "obvious".
 
 Since this PR is a regression (albeit a minor one regarding an error
 message,) I'd like to get it into the branches if possible.
 
 OK for 3.3 and 3.2?
 http://gcc.gnu.org/ml/gcc-patches/2003-03/msg02151.html
 
 		Thanks,
 		--Kaveh
 --
 Kaveh R. Ghazi			ghazi@caip.rutgers.edu


             reply	other threads:[~2003-03-30 19:16 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-30 19:26 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-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  5:16 Kaveh R. Ghazi
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=20030330191601.14103.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).