From: Yao Qi <yao@codesourcery.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: <gdb@sourceware.org>
Subject: Re: --with-babeltrace generates many FAILs
Date: Mon, 18 Aug 2014 06:02:00 -0000 [thread overview]
Message-ID: <53F195E8.6080307@codesourcery.com> (raw)
In-Reply-To: <20140816204614.GA7000@host2.jankratochvil.net>
On 08/17/2014 04:46 AM, Jan Kratochvil wrote:
> since 65c749e7c049f9bf944c5fbe9e727b7a8b4ccc7c (Fix build/17104) babeltrace
> got enabled for me but now I get many new FAILs in testsuites, such as for
> gdb.trace/actions.exp:
> (gdb) target ctf .../gdb/testsuite/gdb.trace/actions.ctf
> [error] Invalid CTF stream: content size is smaller than packet headers.
> [error] Stream index creation error.
> [error] Open file stream error.
> [warning] [Context] Cannot open_trace of format ctf at path .../gdb/testsuite/gdb.trace/actions.ctf.
> Unable to use libbabeltrace on directory ".../gdb/testsuite/gdb.trace/actions.ctf"
> (gdb) PASS: gdb.trace/actions.exp: change to ctf target
> info tracepoints 1
> No tracepoint matching '1'.
> (gdb) info tracepoints 2
> No tracepoint matching '2'.
> (gdb) info tracepoints 3
> No tracepoint matching '3'.
> (gdb) FAIL: gdb.trace/actions.exp: ctf: tracepoint on gdb_c_test
> FAIL: gdb.trace/actions.exp: ctf: tracepoint on gdb_asm_test
> FAIL: gdb.trace/actions.exp: ctf: tracepoint on gdb_recursion_test 0
> testcase ./gdb.trace/actions.exp completed in 2 seconds
>
> Tested with libbabeltrace-1.2.1-2.fc21.x86_64.
> Tested on Fedora 21pre x86_64 (but it looks the same on Fedora 20 x86_64).
>
> I sure can start debugging it but only if you have some idea.
Jan,
I'll take a look today or tomorrow.
--
Yao (é½å°§)
prev parent reply other threads:[~2014-08-18 6:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-16 20:46 Jan Kratochvil
2014-08-18 6:02 ` Yao Qi [this message]
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=53F195E8.6080307@codesourcery.com \
--to=yao@codesourcery.com \
--cc=gdb@sourceware.org \
--cc=jan.kratochvil@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