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 16:29:23 +0100 [thread overview]
Message-ID: <2945958.e9J7NaK4W3@localhost> (raw)
In-Reply-To: <20240130131429.GA786076@pevik>
On Tuesday, January 30, 2024 2:14:29 PM CET Petr Vorel wrote:
> Hi Avinesh,
>
> > Hi Petr,
> >
> > > -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
>
> thanks for having a look!
>
> There is currently no -f parameter, but sure, it could be in the future.
> ./fanotify01 -h # shows no -f parameter
>
> ./fanotify01 -f
> ...
> tst_test.c:688: TBROK: Invalid option
>
> But I meant '-f' as strace parameter, e.g.:
>
> strace -f ./fanotify01
>
> should I wrote this?
>
> To trace test with strace use call strace with `-f` parameter.
yes, or maybe-
To trace the test with strace, use strace with `-f` option to enable tracing
of forked processes also.
Thanks,
Avinesh
>
> Kind regards,
> Petr
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2024-01-30 15:29 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
2024-01-30 13:14 ` Petr Vorel
2024-01-30 15:29 ` Avinesh Kumar [this message]
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=2945958.e9J7NaK4W3@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