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

Jump to bottom

Allow stopping at isolate start events #14227

Closed
iposva-google opened this issue Oct 18, 2013 · 9 comments
Closed

Allow stopping at isolate start events #14227

iposva-google opened this issue Oct 18, 2013 · 9 comments
Assignees
@turnidge
Labels
area-vm Use area-vm for VM related issues, including code coverage, FFI, and the AOT and JIT backends.

Comments

@iposva-google
Copy link
Contributor

When debugging a program with multiple isolates it would be helpful if an isolate start event could pause the isolate being created. That could also just mean to set a breakpoint in the main function entry point for the new isolate, which would keep the start event non-blocking.

There might be a similar need for isolate death events, but I cannot see a good use for that yet.
@iposva-google
Copy link
Contributor Author

cc @mhausner.
Set owner to @turnidge.

@scheglov
Copy link
Contributor

What is the status of this feature?
Is it implemented already?

@turnidge
Copy link
Contributor

I week ago or so I added a --break-at-isolate-spawn flag. It causes each new isolate to take a one-time breakpoint at its entrypoint. This breakpoint is a distinct event from the IsolateCreated notification. Does this help you?

@scheglov
Copy link
Contributor

It would have helped me if it had worked :-)

I've opened an issue yesterday https://code.google.com/p/dart/issues/detail?id=20974

@turnidge
Copy link
Contributor

Devon seemed to be able to use the flag. What problem are you seeing?

@scheglov
Copy link
Contributor

Please see the issue referenced above.

tl;dr: it does not work.

@turnidge
Copy link
Contributor

Please talk to Devon. He was able to use this flag for his purposes. If, after talking to Devon you are still unable to get this to work, then we should have a short VC to discuss this in person rather than continuing this.

@scheglov
Copy link
Contributor

I already discussed this with Devon yesterday.
See https://code.google.com/p/dart/issues/detail?id=20974 for details.

@iposva-google
Copy link
Contributor Author

It seems to me that this works now,

Removed Debugger label.
Added Fixed label.

@iposva-google iposva-google added Type-Defect area-vm Use area-vm for VM related issues, including code coverage, FFI, and the AOT and JIT backends. labels Sep 18, 2014
@iposva-google iposva-google mentioned this issue Jun 4, 2015
Closed
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@turnidge turnidge

Labels
area-vm Use area-vm for VM related issues, including code coverage, FFI, and the AOT and JIT backends.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@kevmoo @scheglov @turnidge @iposva-google