RE: gdb-ui can't handle mutiple debugging sessions

[Zoltan Kemenczy]

Another example where multiple debugging sessions are used is concurrent java / 
c debugging.

In this case a java application (debuggee 1) at some point loads one of the 
native code extensions (shared library, DLL (debugee 2).  The trouble here is 
that, because the native code runs from a shared library, one has to stop the 
java application just after the DLL had been loaded (jdb), and then attach to 
the native code process using gdb to set breakpoints.  While debugging the 
native code, the jdb session is active and waiting for the native code to 
return control...  This can't be performed in a serial fashion.

Regards,
Zoltan Kemenczy

> Message: 4
> Date: Wed, 15 Sep 2004 13:10:06 +0900 (JST)
> From: Kenichi Handa <address@hidden>
> Subject: Re: gdb-ui can't handle mutiple debugging sessions
> To: address@hidden
> Cc: address@hidden, address@hidden, address@hidden
> Message-ID: <address@hidden>
> Content-Type: text/plain; charset=US-ASCII
> 
> In article <address@hidden>, Nick Roberts 
> <address@hidden> writes:
> >>  I'm writing a C library.  I also wrote several programs that
> >>  use that library to test it.  So, it's important for me to
> >>  use a single Emacs session to run those test programs under
> >>  multiple gdb sessions...  
> 
> > Why can't you test the library with your programs in a 
> serial fashion?
> > Do you really need to start the second test before 
> finishing the first?
> 
> Because I must confirm that a bug fix for test 2 doesn't
> break test 1.
> 
> ---
> Ken'ichi HANDA
> address@hidden
>