On Fri, Feb 25, 2011 at 5:32 PM, Rob wrote: > > Unfortunately I have found that gdb sometimes dies: > > ... > > Is there any way pyclewn could detect gdb has exited and restart it > with a run? Ideally gdb wouldn't do this, but all recent versions I > have used have had occasional problems. >
The last pyclewn mercurial changeset I have just entered, fixes this on unix, at least for breakpoints. Start pyclewn with --gdb=/path/to/project_file (the path must start with a '/' or a '.'), and after gdb encounters an internal-error, make sure gdb has terminated. If not, then kill gdb. Then pyclewn is in the same state as after a plain ':Cquit' command and the next gdb command, for example ':Cshow prompt' will spawn a new gdb process where all the breakpoints are restored. -- 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
