Pycharm Debugger – Frames Not Available
Question:
I am having a baffling issue with Pycharm debugger… I am VERY new when it comes to working with the debugger, but I liked the ability to see the variables, etc. of the script to locate and resolve issues. I was making some changes to my directories and the default interpreter… but nothing that would seem to cause the following issue.
I cannot seem to get the variables to show up. I have a traceback showing up, but pycharm debugger just shows “Frame is not available” – so I am not able to troubleshoot to resolve it. See the screenshots below:
Answers:
There doesn’t seem to be any breakpoints activated – there will be frames available to view only when you hit a particular breakpoint as your program executes: you activate them by clicking column between the line # and actual code, like here:
You can read more about PyCharm debugging here.
I realized that I was not working with breakpoints right. What I wanted was the debugger to stop and load all the frames when there was an exception raised, not when a generic breakpoint was hit (as the breakpoint was in a loop that didnt throw an exception on every iteration). In pycharm, once you run the debugger WITHOUT any breakpoints, you can go back and “View Breakpoints” (Cntrl + Shift + F8 on Windows) change check the “Python Exception Breakpoint”. This will cause the debugger to stop and load the frames when an exception is thrown! This was the missing piece in my jumbled mind!
I had the same issue with Pycharm.
The project was working fine, but when debugged, it gave me <frame not available> error.
What worked for me is adding these two environment variables.
PYDEVD_USE_CYTHON=NO
PYDEVD_USE_FRAME_EVAL=NO
Reference – Pavel Karateev @ JetBrains
I had the same issue with PyCharm, but later found out that i had incorrect Debug configuration.
The "Debug configuration" located at menu Run > Debug… > your_test_file > Edit.
In "Edit Configuration Settings" window,
The line "Script path" in configuration should point out the actual location of the your_test_file.py. After I corrected the path, debugger started to work.
I am having a baffling issue with Pycharm debugger… I am VERY new when it comes to working with the debugger, but I liked the ability to see the variables, etc. of the script to locate and resolve issues. I was making some changes to my directories and the default interpreter… but nothing that would seem to cause the following issue.
I cannot seem to get the variables to show up. I have a traceback showing up, but pycharm debugger just shows “Frame is not available” – so I am not able to troubleshoot to resolve it. See the screenshots below:
There doesn’t seem to be any breakpoints activated – there will be frames available to view only when you hit a particular breakpoint as your program executes: you activate them by clicking column between the line # and actual code, like here:
You can read more about PyCharm debugging here.
I realized that I was not working with breakpoints right. What I wanted was the debugger to stop and load all the frames when there was an exception raised, not when a generic breakpoint was hit (as the breakpoint was in a loop that didnt throw an exception on every iteration). In pycharm, once you run the debugger WITHOUT any breakpoints, you can go back and “View Breakpoints” (Cntrl + Shift + F8 on Windows) change check the “Python Exception Breakpoint”. This will cause the debugger to stop and load the frames when an exception is thrown! This was the missing piece in my jumbled mind!
I had the same issue with Pycharm.
The project was working fine, but when debugged, it gave me <frame not available> error.
What worked for me is adding these two environment variables.
PYDEVD_USE_CYTHON=NO
PYDEVD_USE_FRAME_EVAL=NO
Reference – Pavel Karateev @ JetBrains
I had the same issue with PyCharm, but later found out that i had incorrect Debug configuration.
The "Debug configuration" located at menu Run > Debug… > your_test_file > Edit.
In "Edit Configuration Settings" window,
The line "Script path" in configuration should point out the actual location of the your_test_file.py. After I corrected the path, debugger started to work.