public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "wilson at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug debug/24444] [4.1 regression] invalid register in debug info Date: Wed, 19 Oct 2005 23:34:00 -0000 [thread overview] Message-ID: <20051019233436.22763.qmail@sourceware.org> (raw) In-Reply-To: <bug-24444-50@http.gcc.gnu.org/bugzilla/> ------- Comment #2 from wilson at gcc dot gnu dot org 2005-10-19 23:34 ------- This was broken by Richard Henderson's patch that added the convert_cfa_to_loc_list function. The thread for the patch starts here. It was finally installed Sept 7. http://gcc.gnu.org/ml/gcc-patches/2005-08/msg01176.html The flaw with the patch is that Richard modified dwarf2out.c to use the dwarf unwind info unconditionally. However, it is only available for targets that define DWARF2_UNWIND_INFO. For all other targets, we now get incorrect debug info. IA-64 of course has its own unwind info, IA-64 unwind info, as defined by the IA-64 ABI, and does not need or want to use dwarf unwind info. I haven't yet tried to comprehend Richard's patch. It is a big one. Hence, I do not yet have a suggested fix. I suspect the fix may be as simple as putting a #ifdef DWARF2_UNWIND_INFO test in gen_subprogram_die around the convert_cfa_to_loc_list call, and putting the old code back in the #else case. Worst case, we need to write equivalent code that knows how to convert IA-64 unwind info into a location list. However, given that gdb already knows how to use libunwind, and any other self-respecting IA-64 debugger should also already be using the IA-64 unwind info, it isn't clear to me that we need to do anything in gcc here. We can not make the same assumption about dwarf2 unwind info, as this isn't part of the ABI for most targets, so Richard's patch does make sense there. -- wilson at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Ever Confirmed|0 |1 Last reconfirmed|0000-00-00 00:00:00 |2005-10-19 23:34:35 date| | http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24444
next prev parent reply other threads:[~2005-10-19 23:34 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-10-19 17:02 [Bug debug/24444] New: " schwab at suse dot de 2005-10-19 17:03 ` [Bug debug/24444] " schwab at suse dot de 2005-10-19 23:34 ` wilson at gcc dot gnu dot org [this message] 2005-10-20 5:09 ` wilson at gcc dot gnu dot org 2005-10-20 8:36 ` rth at gcc dot gnu dot org 2005-10-21 0:53 ` wilson at gcc dot gnu dot org 2005-10-31 6:32 ` mmitchel at gcc dot gnu dot org 2005-10-31 23:39 ` wilson at gcc dot gnu dot org 2005-10-31 23:46 ` wilson at gcc dot gnu dot org 2005-11-01 1:16 ` wilson at gcc dot gnu dot org 2005-11-15 20:58 ` drow at false dot org 2006-02-03 8:40 ` [Bug debug/24444] [4.1/4.2 " aoliva at gcc dot gnu dot org 2006-02-03 18:49 ` pinskia at gcc dot gnu dot org 2006-02-04 22:08 ` aoliva at gcc dot gnu dot org 2006-02-04 22:13 ` aoliva at gcc dot gnu dot org 2006-02-04 22:23 ` pinskia at gcc dot gnu dot org 2006-02-07 6:51 ` jakub at gcc dot gnu dot org 2006-02-07 6:52 ` jakub at gcc dot gnu dot org 2006-02-21 0:33 ` patchapp at dberlin 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=20051019233436.22763.qmail@sourceware.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).