public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
* Debugging software including background processes
@ 2015-07-28 20:50 SF Markus Elfring
  2015-07-28 21:27 ` Breazeal, Don
  0 siblings, 1 reply; 3+ messages in thread
From: SF Markus Elfring @ 2015-07-28 20:50 UTC (permalink / raw)
  To: gdb

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?

Regards,
Markus

^ permalink raw reply	[flat|nested] 3+ messages in thread

* RE: Debugging software including background processes
  2015-07-28 20:50 Debugging software including background processes SF Markus Elfring
@ 2015-07-28 21:27 ` Breazeal, Don
  2015-07-29  5:32   ` SF Markus Elfring
  0 siblings, 1 reply; 3+ messages in thread
From: Breazeal, Don @ 2015-07-28 21:27 UTC (permalink / raw)
  To: SF Markus Elfring, gdb



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

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: Debugging software including background processes
  2015-07-28 21:27 ` Breazeal, Don
@ 2015-07-29  5:32   ` SF Markus Elfring
  0 siblings, 0 replies; 3+ messages in thread
From: SF Markus Elfring @ 2015-07-29  5:32 UTC (permalink / raw)
  To: Breazeal, Don; +Cc: gdb

> The GDB manual's sections on debugging forks … and on debugging multiple programs … should help with this.

Thanks for your hint.

Are there any attempts to make the debugging of child processes
and several inferiors a bit more convenient by dedicated user interfaces?

Do you know if any scripts can be reused to collect corresponding data
inferiors and child processes in an easier way?

Regards,
Markus

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2015-07-29  5:32 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2015-07-28 20:50 Debugging software including background processes SF Markus Elfring
2015-07-28 21:27 ` Breazeal, Don
2015-07-29  5:32   ` SF Markus Elfring

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).