-
-
Notifications
You must be signed in to change notification settings - Fork 5.7k
Add --trace-eval and Base.TRACE_EVAL for showing each top level eval
#57137
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
Conversation
|
I'm thinking |
|
Seems like this could also be useful in other use cases, e.g. running a long-running HPC job on a computer cluster where you don't have direct access to the process (and thus can't send SIGUSR yourself. |
|
Should/could this use a carriage return instead of a hard newline or something else that's a bit smarter than just printing a new line? It feels like enabling this would be very spammy for longer testsuites. |
|
It's a nice idea, but I'd worry about printing over other prints. Is there a way to determine whether anything has been printed to |
095a4b5 to
cb8d345
Compare
--trace-eval and Base.TRACE_EVAL for showing each top level eval
cb8d345 to
4ccedad
Compare
|
One thing to note. There's no merit in adding a |
1bbb31c to
cfba94e
Compare
|
For the GC there is functions |
|
Probably a good idea yeah. Makes the implementation adjustable behind a function API. |

For debugging purposes makes it possible to see where top level eval is at during a running script or test suite, for debugging slow execution/hangs. Especially on remote machines that are harder to send a
SIGUSR1/SIGINFOto.For instance, the default
loc(ation)mode on a test suite:And with this and the new
JULIA_TEST_VERBOSE#59295