Open jrheisey opened 8 years ago
Thanks for the detailed report. I cannot reproduce this on Linux. @cgchoffman can you reproduce this on Windows? What version of Perl do you have?
@mitchell-as I appear to get the same issue:
@jrheisey Please go to Edit > Preferences > Languages > Perl and then in the "Debugger Logging" section, check "Enable Debugger Log", and browse to/select a location you are familiar with. Then try again to debug. After experiencing the errors, please go to the debug log location you selected previously and send us that log. Thanks so much.
Sorry I left a couple breakpoints for another project in the previous upload. When these are gone I see the same behavior. perl-dbgp.log.txt pystderr.txt
Thanks! I'll have to look into this further when I get the chance.
Dear!
I think I have a very good news, it's gonna be a surprise for you, I am sure you will love it! More info here http://rdozotispo.antoniomcclelland.com/e4tsrt
Take care, tony.attwood
Short Summary
Using breakpoints in functions which are executed in a thread context causes the target script and Komodo to hang or be unresponsive.
Steps to Reproduce
Expected results
I would expect the two breakpoints to repeatedly be triggered every time I click Go in Komodo.
Actual results
This results in Komodo not responding or taking a long time to respond to its own UI events. The target script does not produce any output other than the first iteration in the ThreadOneSubroutine() function.
If you remove the breakpoints and click Go the script runs to completion as expected under Komodo.
Platform Information
Active State Perl 5.8.8 (Yeah I know its old but I am stuck with it for the short term) Komodo Edit or IDE? IDE debugger Komodo Version? version 9.3.2, build 88191, platform win32-x86. Built on Thu Dec 10 11:38:17 2015. Operating System (and version)? Windows 7 64 bit
Additional Information
-- eg. Error logs, screenshots, workarounds --
PerlThreadTest.zip