Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Debugger Get Stack Trace command ignores isolateID parameter #9530

Closed
tomball opened this issue Mar 29, 2013 · 4 comments
Closed

Debugger Get Stack Trace command ignores isolateID parameter #9530

tomball opened this issue Mar 29, 2013 · 4 comments
Labels
area-vm Use area-vm for VM related issues, including code coverage, FFI, and the AOT and JIT backends. P3 A lower priority bug or feature request

Comments

@tomball
Copy link
Contributor

tomball commented Mar 29, 2013

The debugger wire protocol defines the Get Stack Trace command as taking an isolateId parameter. However, in runtime/bin/dbg_message.cc, the message parameters aren't checked, so Isolate::Current() is always used.

@iposva-google
Copy link
Contributor

Added Triaged label.

@tomball
Copy link
Contributor Author

tomball commented Apr 17, 2013

Removed the owner.

@iposva-google
Copy link
Contributor

Set owner to @mhausner.
Added Accepted label.

@tomball tomball added Type-Defect P3 A lower priority bug or feature request area-vm Use area-vm for VM related issues, including code coverage, FFI, and the AOT and JIT backends. labels Oct 21, 2013
@mhausner
Copy link
Contributor

mhausner commented Dec 4, 2015

The wire protocol has been removed. This is obsolete.

@mhausner mhausner closed this as completed Dec 4, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-vm Use area-vm for VM related issues, including code coverage, FFI, and the AOT and JIT backends. P3 A lower priority bug or feature request
Projects
None yet
Development

No branches or pull requests

3 participants