Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Doug Evans <dje@google.com>
Cc: gdb-patches@sourceware.org, tromey@redhat.com,
	ccoutant@google.com,        saugustine@google.com
Subject: Regressions with dwz  [Re: [RFA] Work around binutils/15021]
Date: Thu, 24 Jan 2013 14:59:00 -0000	[thread overview]
Message-ID: <20130124145914.GA32002@host2.jankratochvil.net> (raw)
In-Reply-To: <yjt24nigsohy.fsf@ruffy2.mtv.corp.google.com>

On Thu, 17 Jan 2013 00:21:29 +0100, Doug Evans wrote:
> Regression tested with gdb-generated .gdb_index version 7 (by hacking the
> gdb-under-test to generate version 7), version 8, with dwz, and with gold.

ceb4ee95539d6324ca0f307ba729ea660ed5d1bd is the first bad commit
commit ceb4ee95539d6324ca0f307ba729ea660ed5d1bd
Author: Doug Evans <dje@google.com>
Date:   Wed Jan 23 18:47:47 2013 +0000

        Work around binutils/15021.
        * dwarf2read.c (dwarf2_per_cu_data): Split imported_symtabs and
        type_unit_group out of union s.  All uses updated.
        (read_index_from_section): Watch for index version 8.
        (follow_die_sig): If using .gdb_index version <= 7, record the TU as
        an imported symtab.
        (write_psymtabs_to_index): Increment version number to 8.

        doc/
        * gdb.texinfo (Index Section Format): Document .gdb_index version 8.

Running ./gdb.cp/namespace.exp ...
FAIL: gdb.cp/namespace.exp: whatis C::cOtherFileType
FAIL: gdb.cp/namespace.exp: whatis ::C::cOtherFileType
FAIL: gdb.cp/namespace.exp: print AAA::ALPHA
Running ./gdb.cp/derivation.exp ...
FAIL: gdb.cp/derivation.exp: ptype A::value_type
FAIL: gdb.cp/derivation.exp: whatis A::value_type
FAIL: gdb.cp/derivation.exp: p (A::value_type) 0
FAIL: gdb.cp/derivation.exp: ptype D::value_type
FAIL: gdb.cp/derivation.exp: whatis D::value_type
FAIL: gdb.cp/derivation.exp: p (D::value_type) 0
FAIL: gdb.cp/derivation.exp: ptype E::value_type
FAIL: gdb.cp/derivation.exp: whatis E::value_type
FAIL: gdb.cp/derivation.exp: p (E::value_type) 0
FAIL: gdb.cp/derivation.exp: ptype F::value_type
FAIL: gdb.cp/derivation.exp: whatis F::value_type
FAIL: gdb.cp/derivation.exp: p (F::value_type) 0
FAIL: gdb.cp/derivation.exp: ptype Z::value_type
FAIL: gdb.cp/derivation.exp: whatis Z::value_type
FAIL: gdb.cp/derivation.exp: p (Z::value_type) 0
FAIL: gdb.cp/derivation.exp: ptype ZZ::value_type
FAIL: gdb.cp/derivation.exp: whatis ZZ::value_type
FAIL: gdb.cp/derivation.exp: p (ZZ::value_type) 0
Running ./gdb.base/completion.exp ...
FAIL: gdb.base/completion.exp: complete ptype enum some_

Reproducible on Fedora {18,Rawhide} x86_64 runtest-dwz:

#! /bin/sh
if [ -x ../gdb ];then
  export GDB="$PWD/../gdb -data-directory $PWD/../data-directory"
fi
exec runtest CC_FOR_TARGET=/bin/sh\ $PWD/../contrib/cc-with-tweaks.sh\ -m\ gcc CXX_FOR_TARGET=/bin/sh\ $PWD/../contrib/cc-with-tweaks.sh\ -m\ g++ "$@"

$ runtest-dwz gdb.base/completion.exp gdb.cp/derivation.exp gdb.cp/namespace.exp



Regards,
Jan


  parent reply	other threads:[~2013-01-24 14:59 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-16 23:21 [RFA] Work around binutils/15021 Doug Evans
2013-01-17 17:53 ` Tom Tromey
2013-01-17 18:42   ` Doug Evans
2013-01-17 21:04   ` [RFA, doc RFA] " Doug Evans
2013-01-18  7:17     ` Eli Zaretskii
2013-01-18 14:32     ` Tom Tromey
2013-01-24 14:59 ` Jan Kratochvil [this message]
     [not found]   ` <CADPb22SoND17XeXBL2N+-DXf+yKuWe4PJEXR86qT06-q_LA+7g@mail.gmail.com>
2013-01-24 17:16     ` Regressions with dwz [Re: [RFA] Work around binutils/15021] Jan Kratochvil
2013-01-24 19:08       ` Jan Kratochvil
2013-01-30 20:41         ` Tom Tromey
2013-06-09 17:09 ` [RFA] Work around binutils/15021 Jan Kratochvil
2013-06-12  9:49   ` Doug Evans
2013-06-12 18:29     ` Jan Kratochvil
2013-06-12 19:50       ` Cary Coutant

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=20130124145914.GA32002@host2.jankratochvil.net \
    --to=jan.kratochvil@redhat.com \
    --cc=ccoutant@google.com \
    --cc=dje@google.com \
    --cc=gdb-patches@sourceware.org \
    --cc=saugustine@google.com \
    --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