public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Sylvain.Pion@sophia.inria.fr To: gcc-gnats@gcc.gnu.org Cc: Sylvain.Pion@sophia.inria.fr Subject: debug/6291: Debugging broken on 3.1. GDB says : "Dwarf Error: Cannot handle DW_FORM_strp in DWARF reader." Date: Sat, 13 Apr 2002 16:56:00 -0000 [thread overview] Message-ID: <20020413235223.29646.qmail@sources.redhat.com> (raw) >Number: 6291 >Category: debug >Synopsis: Debugging broken on 3.1. GDB says : "Dwarf Error: Cannot handle DW_FORM_strp in DWARF reader." >Confidential: no >Severity: critical >Priority: medium >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Sat Apr 13 16:56:00 PDT 2002 >Closed-Date: >Last-Modified: >Originator: Sylvain Pion >Release: 3.1 20020411 (prerelease) and 3.2 20020411 (experimental) >Organization: >Environment: RedHat Linux 6.1 (manually upgraded). GDB 5.1 >Description: Debugging information seems totally broken. When I compile a trivial C or C++ program, GDB tells me : Dwarf Error: Cannot handle DW_FORM_strp in DWARF reader. I can't even put a breakpoint on "main". This shows up with current GCC 3.1 and 3.2 (gcc and g++). 2.95.3 and 3.0.4 both work fine. This seems critical for the 3.1 release ! >How-To-Repeat: Compile with "-g", with gcc or g++ the following program: int main() { return 0; } Then run "gdb a.out", and then type "b main" in gdb. >Fix: I don't know of any fix. >Release-Note: >Audit-Trail: >Unformatted:
next reply other threads:[~2002-04-13 23:56 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-04-13 16:56 Sylvain.Pion [this message] 2002-04-13 17:16 Daniel Jacobowitz 2002-04-13 17:26 Andrew Pinski 2002-04-13 17:29 dberlin
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=20020413235223.29646.qmail@sources.redhat.com \ --to=sylvain.pion@sophia.inria.fr \ --cc=gcc-gnats@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).