I think I found two different bugs - one in gdb and that seems to cause a 
problem in pyclewn.

I found that after I am debugging a file, if I use the :Cfile command in 
pyclewn and give it a filename that does not exist, it causes gdb to crash - so 
then I get a message like this to the clewn console window - where I first run 
the file that exists, then try :Cfile on a non-existant file name:


(gdb) file a.out
(gdb) run

Program exited normally.
(gdb) file vlarg
vlarg: No such file or directory.

gdb process terminated with a core dump.
Project './pyclewn.info' not saved: no executable file specified.
Closing this gdb session.

===========
Pyclewn version 1.8.py2 starting a new instance of gdb.


Now - the second bug (in pyclewn), if I now try using Cmapkeys, it does not 
pick up my .pyclewn-keys.gdb file - instead, it uses the default pyclewn keys 
instead.

The problem with gdb doesn't seem to happen outside of pyclewn, so perhaps it 
is specific to the gdb/mi interface.  My gdb version is:

 GNU gdb (GDB) Red Hat Enterprise Linux (7.2-50.el6)

This also brings me to a question - does pyclewn have an equivalent of the 
clewn cl_restart command?  I didn't see it in the documentation.    I still 
have lots of problems with gdb managing to restart itself after I rebuild my 
application, and the clewn cl_restart command overcomes these quite nicely.  I 
was trying to use the file command in its place, that is a pain because I have 
to type the long pathname to the file.  In this case, I mistyped the file and 
then I ran into these problems.

Phil



------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Pyclewn-general mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/pyclewn-general

Reply via email to