Skip to content
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

Debugging is not displaying call stack breakpoint info and variable values #2661

Closed
fanojos opened this issue Sep 23, 2018 · 11 comments
Closed
Labels
area-debugging bug Issue identified by VS Code Team member as probable bug info-needed Issue requires more information from poster

Comments

@fanojos
Copy link

fanojos commented Sep 23, 2018

Environment data

  • VS Code version: 1.27.2
  • Extension version (available under the Extensions sidebar): ms-python.python, donjayamanne.python-extension-pack
  • OS and version: Windows 10 Enterprise, 10.0.17134 N/A Build 17134
  • Python version (& distribution if applicable, e.g. Anaconda): Anaconda 5.2.0
  • Type of virtual environment used (N/A | venv | virtualenv | conda | ...):
 active environment : timeboard-env
    active env location : C:\Users\anaconda\Anaconda3\envs\timeboard-env
            shell level : 2
       user config file : C:\Users\fanos.josephides\.condarc
 populated config files : C:\Users\fanos.josephides\.condarc
          conda version : 4.5.11
    conda-build version : 3.10.5
         python version : 3.6.5.final.0
       base environment : C:\Users\anaconda\Anaconda3  (writable)
           channel URLs : https://repo.anaconda.com/pkgs/main/win-64
                          https://repo.anaconda.com/pkgs/main/noarch
                          https://repo.anaconda.com/pkgs/free/win-64
                          https://repo.anaconda.com/pkgs/free/noarch
                          https://repo.anaconda.com/pkgs/r/win-64
                          https://repo.anaconda.com/pkgs/r/noarch
                          https://repo.anaconda.com/pkgs/pro/win-64
                          https://repo.anaconda.com/pkgs/pro/noarch
                          https://repo.anaconda.com/pkgs/msys2/win-64
                          https://repo.anaconda.com/pkgs/msys2/noarch
          package cache : C:\Users\anaconda\Anaconda3\pkgs
                          C:\Users\fanos.josephides\AppData\Local\conda\conda\pkgs
       envs directories : C:\Users\anaconda\Anaconda3\envs
                          C:\Users\fanos.josephides\AppData\Local\conda\conda\envs
                          C:\Users\fanos.josephides\.conda\envs
               platform : win-64
             user-agent : conda/4.5.11 requests/2.18.4 CPython/3.6.5 Windows/10 Windows/10.0.17134
          administrator : False
             netrc file : None
           offline mode : False
  • Relevant/affected Python packages and their versions:
(timeboard-env) C:\Users\anaconda\Anaconda3\envs\timeboard-env>python --version
Python 3.7.0

Actual behavior

Debugging is not displaying call stack breakpoint info and variable values

Expected behavior

Pause on breakpoint, display the stack and variables used, show the debug yellow label mark for each line code.

Steps to reproduce:

Run below demo:

demo

@brettcannon brettcannon added bug Issue identified by VS Code Team member as probable bug needs verification area-debugging labels Sep 24, 2018
@brettcannon
Copy link
Member

Can you verify, @DonJayamanne ?

@DonJayamanne
Copy link

Works for me, will need to test on a Windows box.
I find this unusual, as we have system tests in PTVSD to check for variables (and those tests run on all three platform with Python 3.7).

@DonJayamanne DonJayamanne removed their assignment Sep 27, 2018
@DonJayamanne DonJayamanne added info-needed Issue requires more information from poster and removed needs verification labels Sep 27, 2018
@DonJayamanne
Copy link

@fanojos
Please could you install the latest development version of the extension from here and test this once again: https://github.com/Microsoft/vscode-python/blob/master/CONTRIBUTING.md#development-build

@DonJayamanne
Copy link

Could be similar to #2769

@DonJayamanne
Copy link

@fanojos
When this fails, please could you provide the contents of the console window, instructions as follows:

  • Go to the command Developer->Toggle Developer Tools in your command palette
  • Check the contents of the Console Window
  • Past the contents in here (on GitHub)

@inved1
Copy link

inved1 commented Oct 5, 2018

I'm having the same errors with
Python 2.7.10
Django 1.8.8
macOS Mojave 10.14

@fanojos
Copy link
Author

fanojos commented Oct 5, 2018

@DonJayamanne see console output

console.ts:136 [Extension Host] Python Extension: Error in debugger Banner Error: Missing required @injectable annotation in: Random.
	at getTargets (C:\Users\fanos.josephides\.vscode\extensions\ms-python.python-2018.8.0\node_modules\inversify\lib\planning\reflection_utils.js:20:15)
	at Object.getDependencies (C:\Users\fanos.josephides\.vscode\extensions\ms-python.python-2018.8.0\node_modules\inversify\lib\planning\reflection_utils.js:11:19)
	at C:\Users\fanos.josephides\.vscode\extensions\ms-python.python-2018.8.0\node_modules\inversify\lib\planning\planner.js:106:51
	at Array.forEach (<anonymous>)
	at _createSubRequests (C:\Users\fanos.josephides\.vscode\extensions\ms-python.python-2018.8.0\node_modules\inversify\lib\planning\planner.js:94:20)
	at Object.plan (C:\Users\fanos.josephides\.vscode\extensions\ms-python.python-2018.8.0\node_modules\inversify\lib\planning\planner.js:129:9)
	at C:\Users\fanos.josephides\.vscode\extensions\ms-python.python-2018.8.0\node_modules\inversify\lib\container\container.js:316:37
	at Container._get (C:\Users\fanos.josephides\.vscode\extensions\ms-python.python-2018.8.0\node_modules\inversify\lib\container\container.js:309:44)
	at Container.get (C:\Users\fanos.josephides\.vscode\extensions\ms-python.python-2018.8.0\node_modules\inversify\lib\container\container.js:228:21)
	at ServiceContainer.get (C:\Users\fanos.josephides\.vscode\extensions\ms-python.python-2018.8.0\out\client\ioc\container.js:28:89)
	at DebuggerBanner.<anonymous> (C:\Users\fanos.josephides\.vscode\extensions\ms-python.python-2018.8.0\out\client\debugger\banner.js:163:55)
	at Generator.next (<anonymous>)
	at C:\Users\fanos.josephides\.vscode\extensions\ms-python.python-2018.8.0\out\client\debugger\banner.js:18:71
	at new Promise (<anonymous>)
	at __awaiter (C:\Users\fanos.josephides\.vscode\extensions\ms-python.python-2018.8.0\out\client\debugger\banner.js:14:12)
	at DebuggerBanner.getDebuggerLaunchThresholdCounter (C:\Users\fanos.josephides\.vscode\extensions\ms-python.python-2018.8.0\out\client\debugger\banner.js:158:16)
	at DebuggerBanner.<anonymous> (C:\Users\fanos.josephides\.vscode\extensions\ms-python.python-2018.8.0\out\client\debugger\banner.js:135:22)
	at Generator.next (<anonymous>)
	at C:\Users\fanos.josephides\.vscode\extensions\ms-python.python-2018.8.0\out\client\debugger\banner.js:18:71
	at new Promise (<anonymous>)
	at __awaiter (C:\Users\fanos.josephides\.vscode\extensions\ms-python.python-2018.8.0\out\client\debugger\banner.js:14:12)
	at DebuggerBanner.passedThreshold (C:\Users\fanos.josephides\.vscode\extensions\ms-python.python-2018.8.0\out\client\debugger\banner.js:133:16)
	at DebuggerBanner.<anonymous> (C:\Users\fanos.josephides\.vscode\extensions\ms-python.python-2018.8.0\out\client\debugger\banner.js:72:30)
	at Generator.next (<anonymous>)
	at C:\Users\fanos.josephides\.vscode\extensions\ms-python.python-2018.8.0\out\client\debugger\banner.js:18:71
	at new Promise (<anonymous>)
	at __awaiter (C:\Users\fanos.josephides\.vscode\extensions\ms-python.python-2018.8.0\out\client\debugger\banner.js:14:12)
	at DebuggerBanner.shouldShow (C:\Users\fanos.josephides\.vscode\extensions\ms-python.python-2018.8.0\out\client\debugger\banner.js:68:16)
	at DebuggerBanner.<anonymous> (C:\Users\fanos.josephides\.vscode\extensions\ms-python.python-2018.8.0\out\client\debugger\banner.js:188:37)
	at Generator.next (<anonymous>)
	at fulfilled (C:\Users\fanos.josephides\.vscode\extensions\ms-python.python-2018.8.0\out\client\debugger\banner.js:15:58)
	at <anonymous>
t.log @ console.ts:136
t._logExtensionHostMessage @ extensionHost.ts:412
(anonymous) @ extensionHost.ts:224
emitTwo @ events.js:126
emit @ events.js:214
emit @ internal/child_process.js:772
_combinedTickCallback @ internal/process/next_tick.js:141
_tickCallback @ internal/process/next_tick.js:180

@DonJayamanne
Copy link

"logToFile": true,
  • Start debugging, once done go into the command palette and select the command Extensions: Open Extensions Folder
  • From there locate the python extension directory ms-python:2018.xxx
  • In that directory look for debug.log, upload the contents of that file here.

@pijaro

This comment has been minimized.

@DonJayamanne

This comment has been minimized.

@brettcannon
Copy link
Member

Because we have not heard back with the information we requested, we are closing this issue for now. If you are able to provide the info later on then we will be happy to re-open this issue to pick up where we left off.

@lock lock bot locked as resolved and limited conversation to collaborators Dec 27, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-debugging bug Issue identified by VS Code Team member as probable bug info-needed Issue requires more information from poster
Projects
None yet
Development

No branches or pull requests

5 participants