Your message dated Thu, 16 Aug 2001 16:13:21 -0400 (EDT)
with message-id <[EMAIL PROTECTED]>
and subject line gcc-2.95 generates bad STABS info on Alpha
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Darren Benham
(administrator, Debian Bugs database)

--------------------------------------
Received: (at submit) by bugs.debian.org; 24 Jul 2001 18:54:07 +0000
>From [EMAIL PROTECTED] Tue Jul 24 13:54:07 2001
Return-path: <[EMAIL PROTECTED]>
Received: from dsl092-073-086.bos1.dsl.speakeasy.net (spawn.hockeyfiend.com) 
[::ffff:66.92.73.86] 
        by master.debian.org with esmtp (Exim 3.12 1 (Debian))
        id 15P7Jn-0003u6-00; Tue, 24 Jul 2001 13:54:07 -0500
Received: from localhost ([127.0.0.1] ident=chris)
        by spawn.hockeyfiend.com with esmtp (Exim 3.31 #1 (Debian))
        id 15P7Jj-0007OX-00
        for <[EMAIL PROTECTED]>; Tue, 24 Jul 2001 14:54:03 -0400
Date: Tue, 24 Jul 2001 14:54:03 -0400 (EDT)
From: "Christopher C. Chimelis" <[EMAIL PROTECTED]>
X-Sender: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: [alpha] gcc-2.95 generates bad STABS debugging info on Alpha
Message-ID: <[EMAIL PROTECTED]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Delivered-To: [EMAIL PROTECTED]


Package: gcc-2.95
Version: 2.95.4-0.010629
Severity: critical

While packaging a new binutils, I noticed that 'strip -g' called twice 
failed to strip binaries that were generated by gcc-2.95, and in fact,
produced binaries that no longer worked (as well as causing strip to
segfault).  This only appears to affect object files, NOT linked binaries,
so stripping archives won't work properly.  When comparing assembly
output, it appears that the stabs info isn't correctly generated.  Using
gcc-3.0 to compile the same file (with the -gstabs option) produced a
correct object file that could be stripped repeatedly without
problems.  Also, using DWARF2 output from gcc-2.95 as well as gcc-3.0 both
worked fine.  I emailed upstream for binutils to verify this and HJ Lu
confirmed that the stabs info doesn't look correct and that binutils was
actually correct.  This appears to only affect Alpha and is holding back a
binutils upload.

This bug is meant as a tracking mechanism for me while I try to fix this
problem, but if someone wants to ask upstream, I can provide asm output
and a very simple testcase.

Binutils that uncovered the problem: 2.11.90.0.24.  2.11.90.0.7 appears to
work fine, but I could reproduce the same problem if I used a certain file
and passed it certain flags.  All gcc-2.95.4 versions that I have (dating
back to April) showed this problem.

C


---------------------------------------
Received: (at 106464-done) by bugs.debian.org; 16 Aug 2001 20:13:22 +0000
>From [EMAIL PROTECTED] Thu Aug 16 15:13:22 2001
Return-path: <[EMAIL PROTECTED]>
Received: from dsl092-073-086.bos1.dsl.speakeasy.net (spawn.hockeyfiend.com) 
[66.92.73.86] (mail)
        by master.debian.org with esmtp (Exim 3.12 1 (Debian))
        id 15XTW6-0001Dv-00; Thu, 16 Aug 2001 15:13:22 -0500
Received: from localhost ([127.0.0.1] ident=chris)
        by spawn.hockeyfiend.com with esmtp (Exim 3.32 #1 (Debian))
        id 15XTW5-0007Py-00
        for <[EMAIL PROTECTED]>; Thu, 16 Aug 2001 16:13:21 -0400
Date: Thu, 16 Aug 2001 16:13:21 -0400 (EDT)
From: "Christopher C. Chimelis" <[EMAIL PROTECTED]>
X-Sender: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: gcc-2.95 generates bad STABS info on Alpha
Message-ID: <[EMAIL PROTECTED]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Delivered-To: [EMAIL PROTECTED]


Turns out that this was a gas problem after all.  Solved in binutils
2.11.90.0.27-1.  For historical reasons, there is something wrong with
what gcc-2.95 outputs, but the problems that I was seeing shouldn't have
been caused by that at all.

C


Reply via email to