From: Sergio Durigan Junior <sergiodj@redhat.com>
To: Pedro Alves <palves@redhat.com>
Cc: Yao Qi <yao@codesourcery.com>, GDB Patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Fix gdb.trace/mi-traceframe-changed.exp to check for target trace support
Date: Fri, 10 Jan 2014 17:31:00 -0000 [thread overview]
Message-ID: <m38uunn3qn.fsf@redhat.com> (raw)
In-Reply-To: <52CFD221.3050100@redhat.com> (Pedro Alves's message of "Fri, 10 Jan 2014 10:57:37 +0000")
On Friday, January 10 2014, Pedro Alves wrote:
>>> The root cause is that tfile.c isn't portable and unable to produce
>>> trace file properly for s390x. Search FIXME in it.
>>
>> Indeed, thanks for pointing that.
>
> Is it the register block size? What's the actual error that
> causes / you're seeing?
The error is:
-trace-find frame-number 0^M
&"PC not available\n"^M
^done,found="1",tracepoint="1",traceframe="0",frame={level="-1",addr="<unavailable>",func="??",args=[]}^M
(gdb) ^M
FAIL: gdb.trace/mi-traceframe-changed.exp: tfile: -trace-find frame-number 0
There is also another error before, but it was already failing for
7.6.2.
--
Sergio
next prev parent reply other threads:[~2014-01-10 17:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-09 21:21 Sergio Durigan Junior
2014-01-10 1:23 ` Yao Qi
2014-01-10 2:17 ` Yao Qi
2014-01-10 3:58 ` Sergio Durigan Junior
2014-01-10 10:57 ` Pedro Alves
2014-01-10 17:31 ` Sergio Durigan Junior [this message]
2014-01-10 18:57 ` Pedro Alves
2014-01-10 20:41 ` Sergio Durigan Junior
2014-01-13 17:12 ` Pedro Alves
2014-01-15 20:37 ` Sergio Durigan Junior
2014-01-16 18:20 ` Pedro Alves
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=m38uunn3qn.fsf@redhat.com \
--to=sergiodj@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.com \
--cc=yao@codesourcery.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).