From: Avinesh Kumar <akumar@suse.de>
To: Petr Vorel <pvorel@suse.cz>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH 1/1] README: Mention -f param for strace
Date: Tue, 30 Jan 2024 13:37:16 +0100 [thread overview]
Message-ID: <12395443.O9o76ZdvQC@localhost> (raw)
In-Reply-To: <20240129174647.635944-1-pvorel@suse.cz>
Hi Petr,
On Monday, January 29, 2024 6:46:47 PM CET Petr Vorel wrote:
> Signed-off-by: Petr Vorel <pvorel@suse.cz>
> ---
> Hi,
>
> probably obvious, but it does not harm to mention it.
> Hopefully users will find it.
>
> Kind regards,
> Petr
>
> README.md | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/README.md b/README.md
> index 6147c5f6f..abbea8f4f 100644
> --- a/README.md
> +++ b/README.md
> @@ -215,12 +215,13 @@ SUSE also publishes a
> [smaller LTP
> container](https://registry.opensuse.org/cgi-bin/cooverview?srch_term=proje
> ct%3D%5Ebenchmark+container%3D.*) that is not based on the Containerfile.
>
> -Debugging with gdb
> -==================
> +Debugging with gdb and strace
> +=============================
>
> The new test library runs the actual test, i.e. the `test()` function in a
> forked process. To get stack trace of a crashing test in gdb it's needed to
> [`set follow-fork-mode
> child`](https://ftp.gnu.org/old-gnu/Manuals/gdb/html_node/gdb_25.html). +To
> trace test with strace use `-f`.
For a second I thought ltp tests has `-f` option.
So maybe if we can make it absolutely clear, or maybe it is just me. :D
Reviewed-by: Avinesh Kumar <akumar@suse.de>
>
> Developers corner
> =================
Thanks,
Avinesh
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2024-01-30 12:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-29 17:46 [LTP] [PATCH 1/1] README: Mention -f param for strace Petr Vorel
2024-01-30 12:37 ` Avinesh Kumar [this message]
2024-01-30 13:14 ` Petr Vorel
2024-01-30 15:29 ` Avinesh Kumar
2024-01-31 18:13 ` Petr Vorel
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=12395443.O9o76ZdvQC@localhost \
--to=akumar@suse.de \
--cc=ltp@lists.linux.it \
--cc=pvorel@suse.cz \
/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