public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hjl at lucon dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug debug/19124] New: [4.0 regression] gcc generates incorrect dwarf2 debug info Date: Wed, 22 Dec 2004 00:36:00 -0000 [thread overview] Message-ID: <20041222003609.19124.hjl@lucon.org> (raw) With gcc 4.0 checked out at Tue Dec 21 23:14:35 UTC 2004, I got [hjl@gnu-10 thread]$ gdb gdb GNU gdb 6.3.0.90_2004-12-14-cvs 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 "i686-pc-linux-gnu"...Using host libthread_db library "/lib/tls/libthread_db.so.1". Setting up the environment for debugging gdb. Breakpoint 1 at 0x8084ce3: file /net/gnu/export/gnu/src/gdb-6.3/gdb/gdb/utils.c, line 849. Breakpoint 2 at 0x80af162: file /net/gnu/export/gnu/src/gdb-6.3/gdb/gdb/cli/cli-cmds.c, line 193. (top-gdb) r /export/build/gnu/gcc/build-i686-linux/gcc/cc1 Starting program: /usr/local/bin/gdb /export/build/gnu/gcc/build-i686-linux/gcc/cc1 GNU gdb 6.3.0.90_2004-12-14-cvs 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 "i686-pc-linux-gnu"...Using host libthread_db library "/lib/tls/libthread_db.so.1". Setting up the environment for debugging gdb. Breakpoint 1 at 0x812d410: file /net/gnu/export/gnu/src/gcc/gcc/gcc/diagnostic.c, line 496. Function "info_command" not defined. (top-gdb) b tls_symbolic_operand Breakpoint 2 at 0x826c1d0: file insn-preds.c, line 471. (top-gdb) r -fpreprocessed foo.i -quiet -dumpbase foo.i -mtune=pentiumpro -auxbase foo -O -version -o foo.s Starting program: /export/build/gnu/gcc/build-i686-linux/gcc/cc1 -fpreprocessed foo.i -quiet -dumpbase foo.i -mtune=pentiumpro -auxbase foo -O -version -o foo.sDetaching after fork from child process 6975. Detaching after fork from child process 6976. GNU C version 4.0.0 20041221 (experimental) (i686-pc-linux-gnu) compiled by GNU C version 4.0.0 20041221 (experimental). GGC heuristics: --param ggc-min-expand=97 --param ggc-min-heapsize=127207 Program received signal SIGSEGV, Segmentation fault. dwarf_expr_frame_base (baton=0xbfffecf0, start=0xbfffec90, length=0xbfffec94) at /net/gnu/export/gnu/src/gdb-6.3/gdb/gdb/dwarf2loc.c:171 171 *length = symbaton->size; (top-gdb) p symbaton $1 = (struct dwarf2_locexpr_baton *) 0x0 [hjl@gnu-10 gcc]$ readelf -w insn-preds.o > /dev/null readelf: Error: Not enough comp units for .debug_loc section [hjl@gnu-10 gcc]$ readelf -w stage1/insn-preds.o > /dev/null It seems that gcc 4.0 generates incorrect .debug_loc section. -- Summary: [4.0 regression] gcc generates incorrect dwarf2 debug info Product: gcc Version: 4.0.0 Status: UNCONFIRMED Severity: critical Priority: P2 Component: debug AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: hjl at lucon dot org CC: gcc-bugs at gcc dot gnu dot org GCC build triplet: i686-pc-linux-gnu GCC host triplet: i686-pc-linux-gnu GCC target triplet: i686-pc-linux-gnu http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19124
next reply other threads:[~2004-12-22 0:36 UTC|newest] Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-12-22 0:36 hjl at lucon dot org [this message] 2004-12-22 0:53 ` [Bug debug/19124] " hjl at lucon dot org 2004-12-22 1:09 ` hjl at lucon dot org 2004-12-22 1:12 ` pinskia at gcc dot gnu dot org 2004-12-22 1:34 ` pinskia at gcc dot gnu dot org 2004-12-22 13:07 ` steven at gcc dot gnu dot org 2004-12-26 0:56 ` dberlin at gcc dot gnu dot org 2004-12-28 2:34 ` pinskia at gcc dot gnu dot org 2004-12-28 18:39 ` hjl at lucon dot org 2004-12-28 18:49 ` dberlin at dberlin dot org 2004-12-30 3:38 ` hjl at lucon dot org 2004-12-30 5:10 ` dberlin at dberlin dot org 2004-12-30 21:01 ` hjl at lucon dot org 2005-01-02 20:29 ` dberlin at gcc dot gnu dot org 2005-01-04 20:07 ` ac131313 at redhat dot com 2005-01-10 16:45 ` dberlin at dberlin dot org 2005-01-10 18:32 ` dberlin at gcc dot gnu dot org 2005-01-10 18:55 ` hjl at lucon dot org 2005-01-10 22:37 ` hjl at lucon dot org 2005-01-20 20:10 ` cvs-commit at gcc dot gnu dot org 2005-01-20 20:15 ` dberlin at gcc dot gnu dot org
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=20041222003609.19124.hjl@lucon.org \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@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).