This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
RE: Debugging software including background processes
- From: "Breazeal, Don" <Don_Breazeal at mentor dot com>
- To: SF Markus Elfring <elfring at users dot sourceforge dot net>, "gdb at sourceware dot org" <gdb at sourceware dot org>
- Date: Tue, 28 Jul 2015 21:27:51 +0000
- Subject: RE: Debugging software including background processes
- Authentication-results: sourceware.org; auth=none
- References: <55B7EB17 dot 1080406 at users dot sourceforge dot 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