From: Hui Zhu <teawater@gmail.com>
To: Pedro Alves <palves@redhat.com>
Cc: Yao Qi <yao@codesourcery.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH] add testsuite for for backtrace commands with tfile to test the tfile memory read
Date: Sun, 24 Jun 2012 07:39:00 -0000 [thread overview]
Message-ID: <CANFwon0=WpGA=VUzZBt0ieui6kWt63AFBtKLf+gwYAKJNZfcxg@mail.gmail.com> (raw)
In-Reply-To: <4FE4353E.2090009@redhat.com>
On Fri, Jun 22, 2012 at 5:05 PM, Pedro Alves <palves@redhat.com> wrote:
> On 06/22/2012 02:42 AM, Hui Zhu wrote:
>
>> On Thu, Jun 21, 2012 at 10:16 PM, Pedro Alves <palves@redhat.com> wrote:
>>> On 06/21/2012 12:15 PM, Hui Zhu wrote:
>>>
>>>>>>
>>>>>> AFAIK, in tfile.exp, trace file is generated by tfile.c and GDB only consumes
>>>>>> these trace files (basic.tf and error.tf) for test purpose.
>>>>>>
>>>> Thanks for your help.
>>>> Post a new version according to your comments.
>>>>
>>>> Thanks,
>>>> Hui
>>>>
>>>> 2012-06-21 Hui Zhu <hui_zhu@mentor.com>
>>>>
>>>> * gdb.trace/tfile.exp: Add new test for backtrace commands
>>>> with tfile to test the tfile memory read.
>>>
>>>
>>> How was this tested?
>
>
>> ?
>
>
> $ make check RUNTESTFLAGS="--target_board=native-gdbserver tfile.exp -v"
> ...
> Skipping tfile.exp because of no fileio capabilities.
> ...
>
> --
> Pedro Alves
This is because:
if [target_info exists gdb,nofileio] {
verbose "Skipping tfile.exp because of no fileio capabilities."
continue
}
So to use this test, need remove "set_board_info gdb,do_reload_on_run 1"
Thanks,
Hui
prev parent reply other threads:[~2012-06-24 7:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-20 10:09 Hui Zhu
2012-06-20 14:19 ` Yao Qi
2012-06-20 14:44 ` Yao Qi
2012-06-21 11:16 ` Hui Zhu
2012-06-21 14:17 ` Pedro Alves
2012-06-22 1:43 ` Hui Zhu
2012-06-22 9:05 ` Pedro Alves
2012-06-24 7:39 ` Hui Zhu [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='CANFwon0=WpGA=VUzZBt0ieui6kWt63AFBtKLf+gwYAKJNZfcxg@mail.gmail.com' \
--to=teawater@gmail.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