forked from DonJayamanne/pythonVSCode
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Support debugging a "pristine" process. #1381
Labels
Comments
ericsnowcurrently
added
feature-request
Request for new features or functionality
area-debugging
needs decision
labels
Apr 12, 2018
brettcannon
pushed a commit
to brettcannon/vscode-python
that referenced
this issue
Jul 18, 2018
* Fix microsoft/vscode#37627 (microsoft#1368) * Version 0.7.0 of extension (microsoft#1381) Archive of 0.7.0 * Update README.md * Update README.md * fix readme * fixes #42 disable in workspace specific config
brettcannon
pushed a commit
to brettcannon/vscode-python
that referenced
this issue
Jul 18, 2018
* Fix microsoft/vscode#37627 (microsoft#1368) * Version 0.7.0 of extension (microsoft#1381) Archive of 0.7.0 * Update README.md * Update README.md * fix readme * merged upstream * disable linting upon extension load
Closing in favor of #1078 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
As noted in #1379, the current default launch config implies that
attach
only works across a network connection. From what I can tell, in fact it only works for processes that were started with the debugger. This excludes debugging processes that were already running without the debugger (i.e. "pristine").Let's say you have a long-running service running on a bunch of hosts (obviously not in your production environment ). On one host you have a particular problem but none of your other hosts have that problem at the moment. The problem happens relatively frequently across your hosts with no apparent pattern and each time before you simply restarted the service. However you've gotten tired of the alerts while on pager duty and decide to get to the bottom of it. You decide to attach the debugger to that process. Obviously you did not start the process with the debugger so all you have is the PID. (Let's leave the whole local/remote issue out of this.) What can you do as a user of the extension?
Environment data
Actual behavior
see above
Expected behavior
see above
Steps to reproduce:
n/a
Logs
n/a
The text was updated successfully, but these errors were encountered: