From: Petr Vorel <pvorel@suse.cz>
To: Cyril Hrubis <chrubis@suse.cz>
Cc: Richard Palethorpe <rpalethorpe@suse.com>, ltp@lists.linux.it
Subject: Re: [LTP] [PATCH 1/1] README: Document gdb debugging
Date: Thu, 12 Oct 2023 11:47:15 +0200 [thread overview]
Message-ID: <20231012094715.GA609744@pevik> (raw)
In-Reply-To: <ZSfAWoGD1ceYPYzW@yuki>
Hi Cyril,
...
> > +Debugging with gdb
> > +==================
> > +
> > +To get stack trace of a crashing test in gdb it's useful to
> > +[`set follow-fork-mode child`](https://ftp.gnu.org/old-gnu/Manuals/gdb/html_node/gdb_25.html).
> Maybe we should start with a sentence that actually describes how things
> are organized so that it's clear why this is needed. Maybe just:
> The new test library runs the actual test, i.e. the `test()` function in
> a forked process. To get the stack trace of a crashing test it's needed
> to [`set ....
+1, thank you.
Kind regards,
Petr
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2023-10-12 9:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-12 9:42 [LTP] [PATCH 1/1] README: Document gdb debugging Petr Vorel
2023-10-12 9:46 ` Cyril Hrubis
2023-10-12 9:47 ` Petr Vorel [this message]
2023-10-23 12:37 ` Cyril Hrubis
2023-10-24 8:24 ` 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=20231012094715.GA609744@pevik \
--to=pvorel@suse.cz \
--cc=chrubis@suse.cz \
--cc=ltp@lists.linux.it \
--cc=rpalethorpe@suse.com \
/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