From: =?gb18030?B?wrfssw==?= <lufei@uniontech.com>
To: =?gb18030?B?Q3lyaWwgSHJ1Ymlz?= <chrubis@suse.cz>
Cc: =?gb18030?B?bHRw?= <ltp@lists.linux.it>
Subject: Re: [LTP] (no subject)
Date: Sun, 28 Apr 2024 15:16:09 +0800 [thread overview]
Message-ID: <tencent_2EA161BC4D09C87A5126A494@qq.com> (raw)
In-Reply-To: tencent_048887541FB562D43FE2D104@qq.com
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="gb18030", Size: 742 bytes --]
It¡¯s fault in my code. supported_archs just works fine.
Sorry.
----------Reply to Message----------
On Fri, Apr 26, 2024 6:30 PM Cyril Hrubis <chrubis@suse.cz> wrote:
Hi!
> I tried using NULL, but met `TBROK: Test killed by SIGSEGV!`.&nbsp;
That means that the manual page is wrong and the address is not ignored.
> And the last time you mentioned in response to using
> `supported_archs`, this seems not work properly by now, the ltp
> document(section of writing_tests) says "not applicable".
The supported_archs is supposed to work. How did you set it (the value)
and what happened?
--
Cyril Hrubis
chrubis@suse.cz
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next parent reply other threads:[~2024-04-28 7:16 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <tencent_048887541FB562D43FE2D104@qq.com>
2024-04-28 7:16 ` =?gb18030?B?wrfssw==?= [this message]
2024-04-19 7:07 [LTP] [PATCH v2] Add case about arch_prctl syscall lufei
2024-04-21 7:15 ` [LTP] (no subject) lufei
2024-04-26 8:36 ` Cyril Hrubis
2024-04-26 9:42 ` 路斐
2024-04-26 10:28 ` Cyril Hrubis
2024-04-26 12:27 ` 路斐
2024-04-26 12:47 ` Jan Stancek
2024-04-28 7:44 ` lufei
-- strict thread matches above, loose matches on Subject: below --
2021-11-15 8:15 Joerg Vehlow
2019-10-07 6:45 Joerg Vehlow
2019-10-07 6:53 ` Joerg Vehlow
2019-08-21 2:25 Jim Woo
2019-08-22 12:45 ` Cyril Hrubis
2014-03-07 11:39 [LTP] [PATCH 1/2] add tst_get_unused_port() Jan Stancek
2014-03-10 14:22 ` [LTP] (no subject) Jan Stancek
2013-08-05 14:44 Stanislav Kholmanskikh
2009-07-01 20:08 Henry Yei
2009-06-24 22:58 Henry Yei
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=tencent_2EA161BC4D09C87A5126A494@qq.com \
--to=lufei@uniontech.com \
--cc=chrubis@suse.cz \
--cc=ltp@lists.linux.it \
/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).