Bug 22295 - [4.0/4.1 Regression] gcc failed to generate debug info
Summary: [4.0/4.1 Regression] gcc failed to generate debug info
Status: RESOLVED DUPLICATE of bug 21828
Alias: None
Product: gcc
Classification: Unclassified
Component: debug (show other bugs)
Version: 4.0.1
: P2 critical
Target Milestone: ---
Assignee: Not yet assigned to anyone
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-07-04 17:45 UTC by H.J. Lu
Modified: 2005-07-23 22:49 UTC (History)
1 user (show)

See Also:
Host:
Target:
Build:
Known to work:
Known to fail:
Last reconfirmed:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description H.J. Lu 2005-07-04 17:45:53 UTC 
On both Linux/ia32 and Linux/x86-64, I got

[hjl@gnu-9 gcc]$ gdb cc1
GNU gdb Red Hat Linux (6.3.0.0-1.21rh)
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "x86_64-redhat-linux-gnu"...Using host libthread_db
library "/lib64/libthread_db.so.1".

Breakpoint 1 at 0x4d6cf5: file
/net/gnu-13/export/gnu/src/gcc-4.0/gcc/gcc/diagnostic.c, line 555.
Breakpoint 2 at 0x4d6c29: file
/net/gnu-13/export/gnu/src/gcc-4.0/gcc/gcc/diagnostic.c, line 496.
Function "exit" not defined.
Function "abort" not defined.
(gdb) watch costs
Hardware watchpoint 3: {<data variable, no debug info>} 10097096

Gcc 3.4 works fine.
Comment 1 Andrew Pinski 2005-07-04 17:54:31 UTC 

*** This bug has been marked as a duplicate of 21828 ***