public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Mike Stump <mrs@apple.com> 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 22:06:00 -0000 [thread overview] Message-ID: <20030325210601.11144.qmail@sources.redhat.com> (raw) The following reply was made to PR other/6955; it has been noted by GNATS. From: Mike Stump <mrs@apple.com> To: Wolfgang Bangerth <bangerth@ticam.utexas.edu> Cc: "Kaveh R. Ghazi" <ghazi@caip.rutgers.edu>, bruno@clisp.org, gcc-bugs@gcc.gnu.org, gcc-gnats@gcc.gnu.org, gcc-patches@gcc.gnu.org Subject: Re: other/6955: collect2 says "core dumped" when there is no core Date: Tue, 25 Mar 2003 12:59:09 -0800 On Tuesday, March 25, 2003, at 09:00 AM, Wolfgang Bangerth wrote: > Well, the line we are talking about is collect2.c:1511. This line has > time > stamp 1999-11-25, CVS version 1.87, which was your commit. Now, I > acknowledge that if I had checked more carefully, then I'd have seen > that > your patch only preserved existing (wrong) behavior, but I haven't > found a > way to get the equivalent of cvs annotate of past versions to see who > really introduced this. cvs diff will tell you. From there, cvs log and look at the comment and the date of the change, and from there, it's back the the ChangeLog entry. Also, the old gcc RCS files can be found on the web site, and can be used to track down things past an old gcc import.
next reply other threads:[~2003-03-25 21:06 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-03-25 22:06 Mike Stump [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 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=20030325210601.11144.qmail@sources.redhat.com \ --to=mrs@apple.com \ --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: 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).