Summary - Late Sunday night must have been sleeping... I think I must have been pressing the button 'Stop debugging and continue running the process' (i.e. the toolbar button on the right side of Stop.)
I updated my ZBS using Git. So ... I've tried: 0.5511 0.6 0.606All of then work to repeatedly hit the break-point when pressing 'Start or Continue debugging' (Left of the Stop button).
However, with the 'Stop debugging and ...' button I get the "Debugger error: unexpected response after 'done'" with 0.5511 and "cannot resume dead coroutine" with 0.6 and 0.606.
I guess your reply on Sunday explains the 0.5511 response. How about the 0.6 / 0.606 response? Is this normal?
Regards, Rob On 28/09/2014 23:08, Paul K wrote:
Hi Rob,require('mobdebug')._VERSION 0.6 The C++ decides to exit, and this is the error that causes that decision...Can you try with the most recent Mobdebug (0.606) either from github or included with ZBS version on github. There was one issue with handling of 'done' command that I fixed recently that affected breakpoints after 'done' and it seems like you may be hitting just that case. Thank you. Paul. On Sun, Sep 28, 2014 at 2:40 PM, Rob Probin<rob.probin@xxxxxxxxx> wrote:So ... require('mobdebug')._VERSION 0.6 The C++ decides to exit, and this is the error that causes that decision...Lua error: ..._man.lua:205: cannot resume dead coroutinestack traceback: [C]: in function 'error' ...thirdparty/mobdebug.lua:649: in function '__div' ...sound_man.lua:205: in function 'add_ADSR_envelope' ...sound_man.lua:245: in function 'make_extra_sounds' ...main.lua:20: in main chunk The breakpoints are in add_ADSR_envelope. Full disclosure: Now, there *may* be other co-routines being used, and some of them are junk (I expect occasionally calling copas.send() outside of a copas thread...) *although* I'm running this in stand alone mode - so it should be calling any of that. (I'll check with the guy who's working on the network code ...) Regards, Rob On 28/09/2014 22:24, Rob Probin wrote:require('mobdebug')._VERSION 0.5511 I'll copy a new one across from my ZBS and give it another go... On 28/09/2014 22:20, Paul K wrote:Hi Rob,I'm pretty sure I didn't get this 'before' ... my project has mobdebug.lua in it and that hasn't changed in forever (git says 7 months ago with the latest version) ... but I've updated my ZBS from git 'a number of weeks ago' ... could this be the problem?That's a bit strange; I would only expect to see something like this if you use a version of mobdebug in your application that doesn't support 'done' command that was added in Mobdebug v0.56. Also, the 'done' command is only sent when you use `Project | Detach Process` command or the toolbar button on the right side of Stop; the IDE doesn't send this command in any other case. So, to trigger this error I can only think of one sequence of steps: (1) you have an old mobdebug in the application and (2) you issue 'done' command from the IDE, which triggers this error. Can you check what version of mobdebug you have in the application? You can type "require('mobdebug')._VERSION" into Remote console after you start debugging. If you indeed using the old version of mobdebug in the application, you can continue using it as all the other commands are compatible, just avoid using 'done' command with it. If you use the same version on both sides and it's 0.56 or later, then I need the exact steps to reproduce as I can't trigger this error in normal circumstances. Paul. On Sun, Sep 28, 2014 at 1:58 PM, Rob Probin<rob.probin@xxxxxxxxx> wrote:Hello, I hit the breakpoint, but when I press continue I get this and never hit the next breakpoint: Debugger error: unexpected response after 'done' Debugging session completed (traced 1 instruction). I'm pretty sure I didn't get this 'before' ... my project has mobdebug.lua in it and that hasn't changed in forever (git says 7 months ago with the latest version) ... but I've updated my ZBS from git 'a number of weeks ago' ... could this be the problem? BFN Rob
