From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Doug Evans <dje@google.com>
Cc: gdb-patches@sourceware.org
Subject: new maint.exp FAIL w/-fdebug-types-section [Re: [RFA 1/2, doc RFA] maint check-symtabs, maint expand-symtabs]
Date: Sun, 19 May 2013 11:23:00 -0000 [thread overview]
Message-ID: <20130519112343.GA1260@host2.jankratochvil.net> (raw)
In-Reply-To: <yjt2k3n2d42c.fsf@ruffy2.mtv.corp.google.com>
On Mon, 13 May 2013 22:20:59 +0200, Doug Evans wrote:
> +# Test "mt expand-symtabs" here as it's easier to verify before we
> +# run the program.
> +gdb_test_no_output "mt set per on" "mt set per on for expand-symtabs"
> +gdb_test_multiple "mt expand-symtabs $subdir/break\[.\]c$" \
> + "mt expand-symtabs" {
> + -re "#primary symtabs: 1 \\(\[+\]1\\),.*$gdb_prompt $" {
> + # This should expand exactly one (primary) symtab.
> + pass "mt expand-symtabs"
> + }
> + }
> +gdb_test "mt set per off" ".*" "mt set per off for expand-symtabs"
$ runtest CC_FOR_TARGET="gcc -gdwarf-4 -fdebug-types-section -g0" gdb.base/maint.exp
FAIL: gdb.base/maint.exp: mt expand-symtabs
mt expand-symtabs gdb.base/break[.]c$
Command execution time: 0.001000 (cpu), 0.000717 (wall)
Space used: 4292608 (+0 for this command)
#symtabs: 11 (+11), #primary symtabs: 2 (+2), #blocks: 9 (+9)
(gdb) FAIL: gdb.base/maint.exp: mt expand-symtabs
Jan
next prev parent reply other threads:[~2013-05-19 11:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-13 20:21 [RFA 1/2, doc RFA] maint check-symtabs, maint expand-symtabs Doug Evans
2013-05-14 14:19 ` Tom Tromey
2013-05-15 15:24 ` Doug Evans
2013-05-15 15:42 ` Eli Zaretskii
2013-05-19 11:23 ` Jan Kratochvil [this message]
2013-05-20 20:27 ` new maint.exp FAIL w/-fdebug-types-section [Re: [RFA 1/2, doc RFA] maint check-symtabs, maint expand-symtabs] Doug Evans
2013-05-24 15:50 ` [RFA 1/2, doc RFA] maint check-symtabs, maint expand-symtabs Tom Tromey
2013-05-30 17:43 ` Tom Tromey
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=20130519112343.GA1260@host2.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=dje@google.com \
--cc=gdb-patches@sourceware.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: 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