{"action":"created","issue":{"url":"https://api.github.com/repos/svaarala/duktape/issues/376","repository_url":"https://api.github.com/repos/svaarala/duktape","labels_url":"https://api.github.com/repos/svaarala/duktape/issues/376/labels{/name}","comments_url":"https://api.github.com/repos/svaarala/duktape/issues/376/comments","events_url":"https://api.github.com/repos/svaarala/duktape/issues/376/events","html_url":"https://github.com/svaarala/duktape/issues/376","id":108153181,"number":376,"title":"Add source map support","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":21,"created_at":"2015-09-24T15:21:48Z","updated_at":"2016-02-23T16:55:34Z","closed_at":null,"body":"I don't know if this has been requested or not before, and would probably not be easy to implement, but I'll throw it out there: Source map support would be useful.  This would allow Duktape to map a position in the source being executed to its position in the original source, helpful for stack traces and such not only for minified code (its obvious application), but transcompiled code as well, e.g. CoffeeScript."},"comment":{"url":"https://api.github.com/repos/svaarala/duktape/issues/comments/187789141","html_url":"https://github.com/svaarala/duktape/issues/376#issuecomment-187789141","issue_url":"https://api.github.com/repos/svaarala/duktape/issues/376","id":187789141,"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-02-23T16:55:34Z","updated_at":"2016-02-23T16:55:34Z","body":"That stepping and breakpoint comment is related to how the semantics of \"step a line\" are defined: we want to trigger when the step is complete, i.e. we transition from \"current line matches breakpoint\" to \"current line doesn't match breakpoint\", and the code is tracking that.\r\n\r\nBut it's all in the interrupt handler, which executes for every instruction, so it's quite easy to muck around with. The interrupt counter is the only mechanism affecting the core executor, and it's always configured to 1 when stepping so that any conditions can be evaluated for every instruction. There's no support for e.g. understanding a line transition in the core executor which is very nice IMO."}}