diff mbox series

[1/1] README: Mention -f param for strace

Message ID 20240129174647.635944-1-pvorel@suse.cz
State Accepted
Headers show
Series [1/1] README: Mention -f param for strace | expand

Commit Message

Petr Vorel Jan. 29, 2024, 5:46 p.m. UTC
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(-)

Comments

Avinesh Kumar Jan. 30, 2024, 12:37 p.m. UTC | #1
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
Petr Vorel Jan. 30, 2024, 1:14 p.m. UTC | #2
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.

Kind regards,
Petr
Avinesh Kumar Jan. 30, 2024, 3:29 p.m. UTC | #3
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
Petr Vorel Jan. 31, 2024, 6:13 p.m. UTC | #4
Hi Avinesh,

...
> > 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.

Make sense, used this and merged.
Thank you!

Kind regards,
Petr
diff mbox series

Patch

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=project%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`.
 
 Developers corner
 =================