{"action":"created","issue":{"url":"https://api.github.com/repos/svaarala/duktape/issues/537","labels_url":"https://api.github.com/repos/svaarala/duktape/issues/537/labels{/name}","comments_url":"https://api.github.com/repos/svaarala/duktape/issues/537/comments","events_url":"https://api.github.com/repos/svaarala/duktape/issues/537/events","html_url":"https://github.com/svaarala/duktape/issues/537","id":126590495,"number":537,"title":"Debugger questions (message semantics)","user":{"login":"fatcerberus","id":4097841,"avatar_url":"https://avatars.githubusercontent.com/u/4097841?v=3","gravatar_id":"","url":"https://api.github.com/users/fatcerberus","html_url":"https://github.com/fatcerberus","followers_url":"https://api.github.com/users/fatcerberus/followers","following_url":"https://api.github.com/users/fatcerberus/following{/other_user}","gists_url":"https://api.github.com/users/fatcerberus/gists{/gist_id}","starred_url":"https://api.github.com/users/fatcerberus/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/fatcerberus/subscriptions","organizations_url":"https://api.github.com/users/fatcerberus/orgs","repos_url":"https://api.github.com/users/fatcerberus/repos","events_url":"https://api.github.com/users/fatcerberus/events{/privacy}","received_events_url":"https://api.github.com/users/fatcerberus/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/svaarala/duktape/labels/debugger","name":"debugger","color":"bfdadc"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":9,"created_at":"2016-01-14T06:44:52Z","updated_at":"2016-01-17T10:05:11Z","closed_at":null,"body":"Despite working directly with the debugger code, I still have a few stupid questions left. :)\r\n\r\nAnyway, I'm currently working on a console debugger a la GDB, which will need to switch between interactive command entry (which is blocking, due to `stdin` line buffering) and waiting for messages (which is also blocking).  Unlike in my GUI debugger, message processing can't happen while waiting for a command, and vice versa.  So my questions are:\r\n\r\n1. Is it safe to assume that, after receiving a Status notify with State=1 (paused), no further messages will be received until the client sends a request?\r\n2. While the target is paused, suppose a request is sent by the client.  Is it then safe to assume no further messages will be received after the reply to this request (REP or ERR)?  Note: This assumes the request in question isn't a Resume.\r\n\r\nIf these assumptions don't hold, then any tips on working around the limitations in play would be appreciated.  Thanks for any help you can provide!"},"comment":{"url":"https://api.github.com/repos/svaarala/duktape/issues/comments/172307606","html_url":"https://github.com/svaarala/duktape/issues/537#issuecomment-172307606","issue_url":"https://api.github.com/repos/svaarala/duktape/issues/537","id":172307606,"user":{"login":"svaarala","id":6377415,"avatar_url":"https://avatars.githubusercontent.com/u/6377415?v=3","gravatar_id":"","url":"https://api.github.com/users/svaarala","html_url":"https://github.com/svaarala","followers_url":"https://api.github.com/users/svaarala/followers","following_url":"https://api.github.com/users/svaarala/following{/other_user}","gists_url":"https://api.github.com/users/svaarala/gists{/gist_id}","starred_url":"https://api.github.com/users/svaarala/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/svaarala/subscriptions","organizations_url":"https://api.github.com/users/svaarala/orgs","repos_url":"https://api.github.com/users/svaarala/repos","events_url":"https://api.github.com/users/svaarala/events{/privacy}","received_events_url":"https://api.github.com/users/svaarala/received_events","type":"User","site_admin":false},"created_at":"2016-01-17T10:05:11Z","updated_at":"2016-01-17T10:05:11Z","body":"For the current implementation that would mostly be the case, but the protocol doesn't guarantee it (black box). And indeed it's quite possible some new commands would cause notifys to be sent during their processing. Eval most likely does that already as you point out, and it's a good example why it'd be very anti-modular not to allow for that."}}