Skip to content

mixed call stacks #19537

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.

Sign up for GitHub

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

Jump to bottom
Closed
jmesserly opened this issue Jun 18, 2014 · 15 comments
Closed

mixed call stacks #19537

jmesserly opened this issue Jun 18, 2014 · 15 comments
Assignees
@jacob314
Labels
closed-not-planned Closed as we don't intend to take action on the reported issue P1 A high priority bug; for example, a single project is unusable or has many test failures
Milestone
1.10

Comments

@jmesserly
Copy link

it doesn't seem possible in Dartium to see the JavaScript frames on the call stack, if you're stopped at a breakpoint or exception where JS is on the stack. This makes it hard to debug typical Polymer apps...
@vsmenon
Copy link
Member

vsmenon commented Jul 4, 2014

Set owner to @jacob314.
Added this to the 1.6 milestone.
Removed Priority-Unassigned label.
Added Priority-High label.

@jmesserly
Copy link
Author

Issue #19744 has been merged into this issue.

@dgrove
Copy link
Contributor

dgrove commented Aug 20, 2014

Is this going to be fixed for 1.6?

@jacob314
Copy link
Member

No. Still waiting for review feedback from vsm. Given the risk level of the
changes, getting it in bleeding edge early in 1.7 is probably best anyway.

@dgrove
Copy link
Contributor

dgrove commented Aug 20, 2014

Removed this from the 1.6 milestone.
Added this to the 1.7 milestone.

@sethladd
Copy link
Contributor

Related: https://code.google.com/p/dart/issues/detail?id=19906

@jacob314
Copy link
Member

This CL won't land in 1.7
Blocked waiting for V8 CL
https://codereview.chromium.org/544143003/
to be reviewed.

1 similar comment
@jacob314
Copy link
Member

This CL won't land in 1.7
Blocked waiting for V8 CL
https://codereview.chromium.org/544143003/
to be reviewed.

@dgrove
Copy link
Contributor

dgrove commented Sep 23, 2014

Removed this from the 1.7 milestone.
Added this to the 1.8 milestone.

@vsmenon
Copy link
Member

vsmenon commented Oct 15, 2014

Removed this from the 1.8 milestone.

@kasperl
Copy link

kasperl commented Nov 28, 2014

Added this to the 1.9 milestone.

@kasperl
Copy link

kasperl commented Nov 28, 2014

Added Accepted label.

@jacob314
Copy link
Member

jacob314 commented Feb 3, 2015

Added Triaged label.

@vsmenon
Copy link
Member

vsmenon commented Mar 3, 2015

Removed this from the 1.9 milestone.
Added this to the 1.10 milestone.

@dgrove
Copy link
Contributor

dgrove commented Apr 17, 2015

Added WontFix label.

@jmesserly jmesserly added Type-Defect P1 A high priority bug; for example, a single project is unusable or has many test failures labels Apr 17, 2015
@jmesserly jmesserly added this to the 1.10 milestone Apr 17, 2015
@kevmoo kevmoo added closed-not-planned Closed as we don't intend to take action on the reported issue and removed resolution-wont_fix labels Mar 1, 2016
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jacob314 jacob314

Labels
closed-not-planned Closed as we don't intend to take action on the reported issue P1 A high priority bug; for example, a single project is unusable or has many test failures
Projects
None yet
Milestone
1.10
Development

No branches or pull requests
7 participants
@sethladd @kevmoo @jmesserly @jacob314 @dgrove @vsmenon @kasperl