public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: "\"Zhou, Wenjian/周文剑\"" <zhouwj-fnst@cn.fujitsu.com>
To: Josh Stone <jistone@redhat.com>
Cc: <systemtap@sourceware.org>, David Smith <dsmith@redhat.com>
Subject: Re: [PATCH 1/3] add testcases for function definitions
Date: Wed, 11 Nov 2015 06:23:00 -0000	[thread overview]
Message-ID: <5642DEAA.20205@cn.fujitsu.com> (raw)
In-Reply-To: <56422AB0.1060200@redhat.com>

On 11/11/2015 01:34 AM, Josh Stone wrote:
> On 11/09/2015 11:06 PM, "Zhou, Wenjian/周文剑" wrote:
>> On 11/10/2015 10:50 AM, "Zhou, Wenjian/周文剑" wrote:
>>> On 11/10/2015 10:31 AM, Josh Stone wrote:
>>>> On 11/09/2015 06:10 PM, "Zhou, Wenjian/周文剑" wrote:
>>>>> To make sure nothing comes, we have to modify all cases which use the
>>>>> stap_run. I don't think it's a good idea that modifying the cases which
>>>>> are working well.
>>>>
>>>> If my probe-final-"EOF" idea works, then we can implement that entirely
>>>> in stap_run, without modifying any testcases.
>>>>
>>>
>>> Eh, if it works, I think the "{5}" won't be needed.
>>> But I doubt whether it will introduce errors to some cases.
>>> I will think more about it.
>>>
>>
>> It works, but also has some side effects.
>> It is better not to affect the cases which are working well, I think.
>
> What are those side effects?
>

It will lead to some cases error.
For example:
In case "div0", the probe will be exit with error.
So the expected "EOF" will never be got.

Another example:
In case "proc_by_pid", if "EOF" is added, another "\r\n" will be needed
in the output_string.

And there are a lot of such problems.
I don't think probe-final-"EOF" is needed, for it won't help much, though
each error it introduces can be fixed easily.

-- 
Thanks
Zhou

  reply	other threads:[~2015-11-11  6:23 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-09  8:58 Zhou Wenjian
2015-11-09  8:58 ` [PATCH 3/3] add more test cases for timer Zhou Wenjian
2015-11-09  8:58 ` [PATCH 2/3] Fix the testcases so that the result will be more exact Zhou Wenjian
2015-11-09 18:07 ` [PATCH 1/3] add testcases for function definitions Josh Stone
2015-11-09 21:24   ` David Smith
2015-11-09 22:21     ` Josh Stone
2015-11-10  2:11   ` "Zhou, Wenjian/周文剑"
2015-11-10  2:31     ` Josh Stone
2015-11-10  2:51       ` "Zhou, Wenjian/周文剑"
2015-11-10  7:07         ` "Zhou, Wenjian/周文剑"
2015-11-10 17:34           ` Josh Stone
2015-11-11  6:23             ` "Zhou, Wenjian/周文剑" [this message]
2015-11-11 14:03               ` Frank Ch. Eigler
2015-11-11 19:07                 ` David Smith
2015-11-12  2:57                   ` "Zhou, Wenjian/周文剑"
2015-11-26  8:43 Zhou Wenjian
2015-12-01  3:21 ` "Zhou, Wenjian/周文剑"
2015-12-04 13:45   ` David Smith

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=5642DEAA.20205@cn.fujitsu.com \
    --to=zhouwj-fnst@cn.fujitsu.com \
    --cc=dsmith@redhat.com \
    --cc=jistone@redhat.com \
    --cc=systemtap@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).