Thank you for your answer. I now use 2 debug sessions, one for the server 
and one for the client.

The server is derived from ThreadingTCPServer (module SocketServer) and 
creates a new thread (located in another module) for each connection.

When I set a breakpoint in the thread handler, then run the server and 
client in debug mode (two separate debug sessions), execution breaks where 
it should, but I do not notice it until I switch from the client debug 
session tab to the server tab.

It would be nice if you received a visual notice (flashing debug session tab 
for example) when execution in a debug session reached a breakpoint.

-Andreas

----- Original Message ----- 
From: "Trent Mick" <trentm@[...].com> 
To: "Andreas Schmid" <monkey@[...].info> 
Cc: <komodo-discuss@[...].com> 
Sent: Friday, April 29, 2005 12:31 AM
Subject: Re: [Komodo-discuss] MSWIN: Multiple instances


>  [Andreas Schmid wrote]
> > Hi,
> >
> > I develop a software package that consists of a client and a server, and 
> > in
> > order to debug the communication between them, I need them to run
> > concurrently.
> >
> > Komodo, does, however, only allow me to open it once, so I can only debug
> > the server OR the client, but not both at the same time.
> >
> > Is there any command line switch that forces it to open a second 
> > instance?
> 
>  Andreas,
> 
>  Komodo supports multiple debug sessions. You should be able to get one
>  debug tab going for each the client and the server.
> 
>  Trent
> 
>  -- 
>  Trent Mick
>  TrentM@[...].com
>  

_______________________________________________
Komodo-discuss mailing list
Komodo-discuss@[...].com
To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
Other options: http://listserv.ActiveState.com/mailman/listinfo/Komodo-discuss