Pyclewn can run multiple consecutive instances of the Gdb class. Each instance of the Gdb class starts a gdb process, maintains gdb/mi state (such as breakpoints, dbgvars, gdb being busy, ....) and dies after the gdb process has terminated. The next Gdb instance does not currently inherit any data from the previous one.
The dbgvars must be created by gdb/MI when gdb is in the proper scope (stopped in the function where the variable is in scope) so it is difficult to restore them. 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. -- 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
