From: Pedro Alves <palves@redhat.com>
To: Sergio Durigan Junior <sergiodj@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 10:57:00 -0000 [thread overview]
Message-ID: <52CFD221.3050100@redhat.com> (raw)
In-Reply-To: <m38uuoo5do.fsf@redhat.com>
On 01/10/2014 03:57 AM, Sergio Durigan Junior wrote:
> On Friday, January 10 2014, Yao Qi wrote:
>
>> Ah, I read the patch and mi-traceframe-change.exp again, and find my
>> last comment is wrong. Sorry for the confusion.
>
> Thank you! I was secretly wondering whether my patch was correct or
> not, because I thought the testcase was intended to be run partially on
> native debugging, as you explained. I was going to e-mail something
> about it tomorrow, but you were faster :-).
>
>> The first half of mi-traceframe-changed.exp (test_tfind_tfile) is to
>> test "=traceframe-changed" on tfile target, which is produced by
>> tfile.c. It is expected to run on native debugging. The second half
>> of mi-traceframe-changed.exp (test_tfile_remote) is to test
>> "=traceframe-changed" on remote target with a gdbserver connected. We
>> can see mi-traceframe-changed.exp has already have the code to check
>> target supports tracing or not.
>>
>> 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?
>> We should skip test_find_tfile for targets other than x86-linux or
>> x86_64-linux. Alternatively, we can modify tfile.c for s390x, but I
>> think "generating tfile on a unsupported-tracing target" isn't useful.
>
> OK, WDYT of this version then?
--
Pedro Alves
next prev parent reply other threads:[~2014-01-10 10:57 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 [this message]
2014-01-10 17:31 ` Sergio Durigan Junior
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=52CFD221.3050100@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=sergiodj@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).