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

[Zoltan Kemenczy]

No.  And my emacs is a snapshot from CVS on Sep 1, built using mingw (not 
cygwin).

Ofcourse, jdb (in *gud-javadebug*) is 'dead' while I'm e.g single-stepping 
native (C) code (as expected), and as soon as I do 'cont' in gdb (in *gud*), my 
*gud-javadebug* gets control back...

What kind of problems should I be looking for? I am not using gdb-ui in any way 
during the above.
My original email was just to point out a need for supporting multiple gud 
session within emacs...

Zoltan

P.S.: It took me a while to 'dust'-off the java/native c code application.  
Loading native dlls built with later cygwin gccs (starting at version 3.3.1) 
fails with JDK 1.4.2, so I had to go back to gcc 3.2 prerelease which still 
works with this JDK.

> -----Original Message-----
> From: Stefan Monnier [mailto:address@hidden
> Sent: September 15, 2004 6:17 PM
> To: Zoltan Kemenczy
> Cc: Nick Roberts; address@hidden
> Subject: Re: gdb-ui can't handle mutiple debugging sessions
> 
> 
> > Yes. For the java application I used M-x jdb with the 
> default 'jdb -attach
> > javadebug' parameters, and M-x gdb used 'gbd -fullname' 
> (the 'attach' and
> > 'dll' gdb commands are used subsequently in the *gud* 
> buffer to specify
> > the dll file and process id).
> > I was able to do this with emacs-CVS and and emacs-21.3.
> 
> And after the M-x gdb step, have you noticed any problems in 
> the jdb buffer?
> 
> 
>         Stefan
>