This is the mail archive of the gdb@sourceware.org mailing list for the GDB project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Multiple inferiors and memory consumption

From: <Paul_Koning at Dell dot com>
To: <marc dot khouzam at ericsson dot com>
Cc: <vladimir at codesourcery dot com>, <gdb at sourceware dot org>
Date: Tue, 10 Jul 2012 20:59:35 +0000
Subject: Re: Multiple inferiors and memory consumption
References: <4FFB3F86.2000109@codesourcery.com> <F7CE05678329534C957159168FA70DEC59791E004D@EUSAACMS0703.eamcs.ericsson.se>

On Jul 10, 2012, at 4:35 PM, Marc Khouzam wrote:

> 
>> And now for my real question -- is there any case when using 
>> multi-process to debug several applications
>> not related via parent-child relationship is better than 
>> running N copies of GDB?
> 
> For the sake of completeness, let me mention the obvious.
> When doing remote debugging, only one GDB can connect
> to the target, so multi-process is the only option to debug
> several applications.

True if you have a centralized stub.  If you have gdbserver implemented, you can run multiple instances of that, OS permitting.

	paul

References:
- Multiple inferiors and memory consumption
  - From: Vladimir Prus
- RE: Multiple inferiors and memory consumption
  - From: Marc Khouzam

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]