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

introduce CONFIG.skip_all #665

Merged
merged 1 commit into from
Jun 30, 2022
Merged

introduce CONFIG.skip_all #665

merged 1 commit into from
Jun 30, 2022

Conversation

ko1
Copy link
Collaborator

@ko1 ko1 commented Jun 30, 2022

CONFIG.skip_all is called to ignore cleanup code.

fix #552

`CONFIG.skip_all` is called to ignore cleanup code.

fix #552
@ko1 ko1 merged commit a773f43 into master Jun 30, 2022
@ko1 ko1 deleted the fix_552 branch June 30, 2022 08:00
@@ -18,7 +18,7 @@ def self.setup debug_port
end

at_exit do
CONFIG[:skip_path] = [//] # skip all
CONFIG.skip_all
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's not really a user configuration but a debugger's internal controlling state. So I think DEBUGGER__.skip? is a better place for this method.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sorry what is DEBUGGER__.skip? and how to use it for here?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I meant instead of defining on CONFIG, it can be defined on DEBUGGER__. Because it actually has nothing to do with the configuration.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I see. It seems better.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

Debugger stops at unexpected places.
2 participants