-
-
Notifications
You must be signed in to change notification settings - Fork 30.5k
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
pdb should check if the executing file is modified and warn users #111051
Labels
Comments
iritkatriel
pushed a commit
that referenced
this issue
Jan 25, 2024
aisk
pushed a commit
to aisk/cpython
that referenced
this issue
Feb 11, 2024
I often have an issue with the test for this when running on a RAM disk formatted with HFS+. That file system only has 1-second mtime resolution, so the test often doesn't register an mtime change and intermittently fails. Fix incoming. |
ambv
added a commit
to ambv/cpython
that referenced
this issue
Jul 22, 2024
ambv
added a commit
that referenced
this issue
Jul 22, 2024
miss-islington
pushed a commit
to miss-islington/cpython
that referenced
this issue
Jul 22, 2024
…w-resolution mtime (pythonGH-121959) (cherry picked from commit cad11a2) Co-authored-by: Łukasz Langa <lukasz@langa.pl>
serhiy-storchaka
pushed a commit
that referenced
this issue
Aug 12, 2024
Glyphack
pushed a commit
to Glyphack/cpython
that referenced
this issue
Sep 2, 2024
Hi @ambv , is this fixed now? Can we close this? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Feature or enhancement
Proposal:
It's possible that the file is modified during debugging, which would definitely confuse users - the source will not match the execution anymore.
There's no perfect solution under such circunstances, but we should at least warn users that this is happening.
Has this already been discussed elsewhere?
This is a minor feature, which does not need previous discussion elsewhere
Links to previous discussion of this feature:
No response
Linked PRs
pdb
#111052The text was updated successfully, but these errors were encountered: