vscode-python: Breakpoints not hit.

Issue Type: Bug

I have a simple file parser in python and input text file. When I place a breakpoint at any line in the soure, the break point is not being hit.

I set the break point at line pointed to here. Or at any line for that matter…

      if m1 != None: #program block begin      
        lnlst.append(line)
    else: #existing list
      if m1 is not None or m2 is not None: #program block begin or final block
        for item in lnlst:
          for fails in flist:
            ptrn = "(\\"+fails[1]+")"+"(.*)"  <<<<<<<<
            match = re.search(ptrn,item)
            if match != None: 
              errFound = True

[forcheck.zip](https://github.com/microsoft/vscode/files/4834297/forcheck.zip)

I expect the debugger to stop and allow me to inspect the variables. I initially created a Microsoft bug for vscode and I was asked to submit this to vscode-python: https://github.com/microsoft/vscode/issues/101075

VS Code version: Code 1.46.1 (cd9ea6488829f560dc949a8b2fb789f3cdc05f5d, 2020-06-17T21:13:20.174Z) OS version: Windows_NT x64 10.0.18363

System Info

Item	Value
CPUs	Intel® Core™ i7-8850H CPU @ 2.60GHz (12 x 2592)
GPU Status	2d_canvas: enabled flash_3d: enabled flash_stage3d: enabled flash_stage3d_baseline: enabled gpu_compositing: enabled multiple_raster_threads: enabled_on oop_rasterization: disabled_off protected_video_decode: enabled rasterization: enabled skia_renderer: disabled_off_ok video_decode: enabled viz_display_compositor: enabled_on viz_hit_test_surface_layer: disabled_off_ok webgl: enabled webgl2: enabled
Load (avg)	undefined
Memory (System)	31.72GB (15.84GB free)
Process Argv
Screen Reader	no
VM	0%

Extensions (14)

Extension	Author (truncated)	Version
vscode-markdownlint	Dav	0.36.0
xml	Dot	2.5.0
vscode-solution-explorer	fer	0.3.10
vscode-pull-request-github	Git	0.17.0
fortran-ls	han	0.6.2
linter-gfortran	krv	2.2.1
vscode-azureappservice	ms-	0.17.0
vscode-docker	ms-	1.3.1
python	ms-	2020.6.90262
remote-wsl	ms-	0.44.4
azure-account	ms-	0.8.11
cpptools	ms-	0.28.3
powershell	ms-	2020.6.0
sourcery	sou	0.2.5

Output from Console under the Developer Tools panel (toggle Developer Tools on under Help; turn on source maps to make any tracebacks be useful by running Enable source map support for extension debugging)

XXXX

About this issue

Original URL
State: closed
Created 4 years ago
Comments: 15

Most upvoted comments

Can this be opened again? The workaround of not activating the python environment in the shell is not working and it is important for me to be able to debug the specific versions in my virtualenv

leo-paz on Jan 16, 2021