On Mon, Mar 21, 2011 at 2:44 PM, Rob wrote:
>
> gdb process terminated after receiving signal 11.
> Closing this gdb session.
>
> ===========
> Pyclewn version 1.5 starting a new instance of gdb.
>
> Quit
> gdb busy: command discarded, please retry
> gdb busy: command discarded, please retry
> gdb busy: command discarded, please retry
>
> Despite what the (clewn)_console says there is no gdb process
> running, and any command such as Crun results in the above busy
> message.
>
Thanks for the follow up. What happened is that everything went just
fine: pyclewn detected the gdb crash and closed the current session.
But it happens that the next command that starts a new session and
spawns a new gdb instance is Csigint or <Ctl-Z> (as can be seen from
the "Quit" line on the console). This kills the new gdb instance
because gdb is starting and has not yet got a chance to setup its
signal handling. For some reason pyclewn does not detect that gdb has
died on this second occurence. Also obviously pyclewn should not
allow to start a new session with Csigint (or even worse Cquit).
So this is another bug and it is easy to reproduce:
* start a gdb session
* Cquit to close the session
* Csigint to start the new session
* Crun
* Crun produces "gdb busy: command discarded, please retry"
Thanks again for your report.
I will fix it shortly.
--
Xavier
Les Chemins de Lokoti: http://lokoti.alwaysdata.net
------------------------------------------------------------------------------
Enable your software for Intel(R) Active Management Technology to meet the
growing manageability and security demands of your customers. Businesses
are taking advantage of Intel(R) vPro (TM) technology - will your software
be a part of the solution? Download the Intel(R) Manageability Checker
today! http://p.sf.net/sfu/intel-dev2devmar
_______________________________________________
Pyclewn-general mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/pyclewn-general
