public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: a.bocaniciu@computer.org To: gcc-gnats@gcc.gnu.org Subject: target/7032: arm-elf-gcc 3.1 generates wrong DWARF-2, unlike 3.0.4 Date: Fri, 14 Jun 2002 09:06:00 -0000 [thread overview] Message-ID: <20020614140218.19655.qmail@sources.redhat.com> (raw) >Number: 7032 >Category: target >Synopsis: arm-elf-gcc 3.1 generates wrong DWARF-2, unlike 3.0.4 >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Fri Jun 14 07:06:02 PDT 2002 >Closed-Date: >Last-Modified: >Originator: Adrian Bocaniciu >Release: arm-elf-gcc version 3.1 >Organization: >Environment: Cross-compiler configured for --target=arm-elf, hosted on i686-pc-cygwin. However, it does not seem likely that the host may have any influence. >Description: Any executable file built from objects compiled with "-g" by arm-elf-gcc 3.1 crashes the ARM Ltd. debugger AXD when trying to load them. The same files compiled with arm-elf-gcc 3.0.4 work perfectly. If I remove from the executable both sections .debug_info and .debug_line, the file can be loaded without problems, but that is not useful, since essential debug information is stripped. If any of the two sections is not removed, the AXD debugger crashes with the same uninteligible error message ("DBE Warning 00255: WIN32 exception code 0xc0000005 was caught in dbess_image\dbt_image.cpp:160"; even if the message says it is a warning, the debugger becomes unusable and must be closed and restarted). >How-To-Repeat: Compile any file with "-g" option using arm-elf-gcc 3.1 and try to load it with ARM Ltd. AXD debugger. >Fix: In order to find the location of the bug, one must search what has changed between V3.0.4 and V3.1 in the generation of the sections .debug_info and .debug_line for the target arm-elf >Release-Note: >Audit-Trail: >Unformatted:
reply other threads:[~2002-06-14 14:06 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20020614140218.19655.qmail@sources.redhat.com \ --to=a.bocaniciu@computer.org \ --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).