Debugger-specific args not being stripped out in experimental debugger
See original GitHub issueI’m defining a simple excepthook
callback to log any unhandled exceptions raised in my python code. When I run the main application with Debug->Start Debugging
the except hook works as expected. However the Without
debugging mode somehow interferes and I don’t see my print message or the exception information logged to my debug log. I’m on a Mac OSX if that matters.
Issue Analytics
- State:
- Created 5 years ago
- Comments:7 (1 by maintainers)
Top Results From Across the Web
Xcode 13: Active breakpoint turns to an outline when app is run.
The compiler generates debug information that is not stripped out (check the Build Settings). The library for the breakpoint is loaded. Posted 5...
Read more >A Time Travelling Debugger for Python
Abstract. Time travelling debuggers (TTD) allow programmers to step backwards through the execution of their program, helping them to explore code and find ......
Read more >Command-Line Reference | Bazel
print_action, Prints the command line args for compiling a file. ... option to add some profiler/debugger-specific JVM startup flags.
Read more >Command-Line Reference - Bazel 1.2.0
print_action, Prints the command line args for compiling a file. ... Convenience option to add some profiler/debugger-specific JVM startup flags.
Read more >Debug Node.js Apps using Visual Studio Code
can be used for the runtimeExecutable attribute and arguments can be passed via runtimeArgs . You do not have to set the program...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Looks good!
launch.json
Unhandled message in log file
VSCode Version 1.27.2
Python Extension 2018.8.0
@jxramos This issue has been resolved, please could you install the latest development version of the extension from here and validate it https://github.com/Microsoft/vscode-python/issues/1385