On Fri, Feb 25, 2011 at 10:58 PM, Xavier de Gaye wrote: > > Currently, it is possible to use the "project" command to backup the > breakpoints to a file. When pyclewn has been started with the proper > command line argument (for example --gdb=/path/to/project_file) and > assuming breakpoints had been saved before the gdb internal-error with > the project command, then this next Gdb instance will start with all > the saved breakpoints as they were set in the previous one. >
The above assumes that a new Gdb instance restarts in all cases, this is not correct. When the gdb process is killed (for example), the asyncore mechanism does not detect it (while it does on the normal termination of gdb) and pyclewn remains unaware of this event. So following your suggestion, pyclewn should monitor the status of the gdb process in the background and warn the user and enable the "project" and "quit" commands when it notices that the gdb process has terminated unexpectedly to avoid being stuck in a deadlock. I will implement a patch shortly. -- Xavier Les Chemins de Lokoti: http://lokoti.alwaysdata.net ------------------------------------------------------------------------------ Free Software Download: Index, Search & Analyze Logs and other IT data in Real-Time with Splunk. Collect, index and harness all the fast moving IT data generated by your applications, servers and devices whether physical, virtual or in the cloud. Deliver compliance at lower cost and gain new business insights. http://p.sf.net/sfu/splunk-dev2dev _______________________________________________ Pyclewn-general mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/pyclewn-general
