From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Cary Coutant <ccoutant@google.com>
Cc: Tom Tromey <tromey@redhat.com>,
gdb-patches@sourceware.org, Doug Evans <dje@google.com>
Subject: Regression for .debug_types [Re: [patch] Allow dummy CUs created by incremental linker]
Date: Thu, 20 Oct 2011 15:00:00 -0000 [thread overview]
Message-ID: <20111020145541.GA31871@host1.jankratochvil.net> (raw)
In-Reply-To: <CAHACq4rhveVSHWaxUCVLPEr5zP+AugfF15=kXiFS0QXWnr6E+A@mail.gmail.com>
On Wed, 19 Oct 2011 17:27:18 +0200, Cary Coutant wrote:
> Done, and committed. Thanks!
99374fd95e942049103b51b4d125c6a4adc38c50 is the first bad commit
commit 99374fd95e942049103b51b4d125c6a4adc38c50
Author: Cary Coutant <ccoutant@google.com>
Date: Wed Oct 19 15:26:27 2011 +0000
* dwarf2read.c (peek_abbrev_code): New function.
(dw2_get_file_names): Check for dummy compilation units.
(create_debug_types_hash_table): Likewise.
(process_psymtab_comp_unit): Likewise.
(load_partial_comp_unit): Likewise.
(load_full_comp_unit): Likewise.
I did not debug it yet but it is a regression for many testcases iff
.debug_types are used. Such as:
FAIL: gdb.base/call-ar-st.exp: print print_small_structs (pattern 6)
FAIL: gdb.base/call-ar-st.exp: step into print_long_arg_list
FAIL: gdb.base/call-ar-st.exp: print print_small_structs from print_long_arg_list (pattern 6)
FAIL: gdb.base/call-ar-st.exp: print print_bit_flags_combo from init_bit_flags_combo
FAIL: gcc (GCC) 4.6.2 20111018 (prerelease)
FAIL: PATH="$HOME/redhat/gcc46-root/bin:$PATH" runtest CC_FOR_TARGET="gcc -gdwarf-4 -g0" CXX_FOR _TARGET="g++ -gdwarf-4 -g0" gdb.base/call-ar-st.exp
FAIL: gcc (GCC) 4.7.0 20111018 (experimental)
FAIL: PATH="$HOME/redhat/gcchead-root/bin:$PATH" runtest CC_FOR_TARGET="gcc -gdwarf-4 -fdebug-types-section -g0" CXX_FOR_TARGET="g++ -gdwarf-4 -fdebug-types-section -g0" gdb.base/call-ar-st.exp
PASS: PATH="$HOME/redhat/gcchead-root/bin:$PATH" runtest CC_FOR_TARGET="gcc -gdwarf-4 -fno-debug-types-section -g0" CXX_FOR_TARGET="g++ -gdwarf-4 -fno-debug-types-section -g0" gdb.base/call-ar-st.exp
Thanks,
Jan
next prev parent reply other threads:[~2011-10-20 14:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-19 0:44 [patch] Allow dummy CUs created by incremental linker Cary Coutant
2011-10-19 15:27 ` Tom Tromey
2011-10-19 15:52 ` Cary Coutant
2011-10-20 15:00 ` Jan Kratochvil [this message]
2011-10-20 19:16 ` Regression for .debug_types [Re: [patch] Allow dummy CUs created by incremental linker] Cary Coutant
2011-10-20 22:35 ` Cary Coutant
2011-10-21 0:00 ` Jan Kratochvil
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=20111020145541.GA31871@host1.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=ccoutant@google.com \
--cc=dje@google.com \
--cc=gdb-patches@sourceware.org \
--cc=tromey@redhat.com \
/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: link
Be 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