Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Yao Qi <yao@codesourcery.com>
To: <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Check tracefile is generated by binary execution
Date: Thu, 10 Apr 2014 02:57:00 -0000	[thread overview]
Message-ID: <5346080B.8060107@codesourcery.com> (raw)
In-Reply-To: <533A2333.8060700@codesourcery.com>

On 04/01/2014 10:23 AM, Yao Qi wrote:
> On 03/25/2014 03:52 PM, Yao Qi wrote:
>> In gdb.trace/tfile.exp, we execute binary to generate tracefile,
>>
>>   remote_exec target "$binfile"
>>
>> however, this fails on bare metal target.  This patch is to
>> handle binary execution failure by running binary in GDB.
>> The binary will do some io operation to generate tracefile, so
>> we need a check 'target_info exists gdb,nofileio'.
>>
>> This patch is to check whether tracefile is generated.  tfile.exp can
>> be skipped if generation is failed, while test_tfind_tfile in
>> mi-traceframe-changed.exp is skipped if generated failed.  The rest of
>> the mi-traceframe-changed.exp can still be executed, because on some
>> bare metal targets, the remote stub may support tracepoint but doesn't
>> support fileio.
>>
>> This patch is tested on nios2-elf and arm-none-eabi.
>>
>> gdb/testsuite:
>>
>> 2014-03-25  Yao Qi  <yao@codesourcery.com>
>>
>> 	* lib/trace-support.exp (generate_tracefile): New procedure.
>> 	* gdb.trace/tfile.exp: Skip the test if generate_tracefile
>> 	return 0.
>> 	* gdb.trace/mi-traceframe-changed.exp: Invoke test_tfind_tfile
>> 	if generate_tracefile returns 1.
> 
> Ping.  https://sourceware.org/ml/gdb-patches/2014-03/msg00591.html
> 

Ping^2.

-- 
Yao (齐尧)


  reply	other threads:[~2014-04-10  2:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-25  7:55 Yao Qi
2014-04-01  2:26 ` Yao Qi
2014-04-10  2:57   ` Yao Qi [this message]
2014-04-21 23:04 ` Stan Shebs
2014-04-22  2:23   ` Yao Qi

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=5346080B.8060107@codesourcery.com \
    --to=yao@codesourcery.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