From: "Breazeal, Don" <Don_Breazeal@mentor.com>
To: SF Markus Elfring <elfring@users.sourceforge.net>,
"gdb@sourceware.org" <gdb@sourceware.org>
Subject: RE: Debugging software including background processes
Date: Tue, 28 Jul 2015 21:27:00 -0000 [thread overview]
Message-ID: <DA279C53C4A5884A907135DFCD7A059A37DCF198@NA-MBX-04.mgc.mentorg.com> (raw)
In-Reply-To: <55B7EB17.1080406@users.sourceforge.net>
> -----Original Message-----
> From: gdb-owner@sourceware.org [mailto:gdb-owner@sourceware.org] On
> Behalf Of SF Markus Elfring
> Sent: Tuesday, July 28, 2015 1:51 PM
> To: gdb@sourceware.org
> Subject: Debugging software including background processes
>
> Hello,
>
> I would like to debug specific software occasionally which uses also
> background processes (on my openSUSE Tumbleweed system).
>
> * Can the tool "gdb 7.9-3.1" be configured to start detailed debugging
> if another background process will be started?
>
> * How can a corresponding backtrace be collected and analysed if a
> subprocess
> might have failed by a segmentation fault for example?
Markus,
The GDB manual's sections on debugging forks(https://sourceware.org/gdb/onlinedocs/gdb/Forks.html) and on debugging multiple programs (https://sourceware.org/gdb/onlinedocs/gdb/Inferiors-and-Programs.html#Inferiors-and-Programs) should help with this. The Linux core(5) man page has information on naming core files that might also help.
--Don
next prev parent reply other threads:[~2015-07-28 21:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-28 20:50 SF Markus Elfring
2015-07-28 21:27 ` Breazeal, Don [this message]
2015-07-29 5:32 ` SF Markus Elfring
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=DA279C53C4A5884A907135DFCD7A059A37DCF198@NA-MBX-04.mgc.mentorg.com \
--to=don_breazeal@mentor.com \
--cc=elfring@users.sourceforge.net \
--cc=gdb@sourceware.org \
/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