Hi,
Unfortunately I have found that gdb sometimes dies:
gdb DEBUG 181-var-update *
gdb DEBUG (gdb)
gdb DEBUG &"gdbtypes.c:1385: internal-error: check_typedef: Assertion `type'
failed.\nA problem internal to GDB has been detected,\nfurther debugging may
prove unreliable."
gdb INFO gdbtypes.c:1385: internal-error: check_typedef: Assertion `type'
failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
gdb DEBUG &"\n"
gdb INFO
in the log, and a message about a gdb core dump appears in a vim window.
However once this has happened there is no way for pyclewn to recover and I
have to restart, losing all breakpoints and dbgvars. Most pyclewn commands
result in "gdb busy: command discarded, please retry" although interrupt gives
"Quit" in the console.
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.
thanks,
Rob
pyclewn 1.5, gdb 7.2
------------------------------------------------------------------------------
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
