Skip to content

Debugging failing when stoponentry=true #4380

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

Closed
Sandy921 opened this issue Feb 13, 2019 · 1 comment
Closed

Debugging failing when stoponentry=true #4380

Sandy921 opened this issue Feb 13, 2019 · 1 comment

Comments

@Sandy921
Copy link

Issue Type: Bug

In Launch.Json file , StoponEntry=true is this not working., when ever user has pressed PF5 the program isn't stopped in first line of code. previously it was working fine.
reference : #68630 in gitHub

Extension version: 2019.1.0
VS Code version: Code 1.31.1 (1b8e8302e405050205e69b59abb3559592bb9e60, 2019-02-12T02:20:54.427Z)
OS version: Windows_NT x64 6.1.7601

System Info
Item Value
CPUs Intel(R) Core(TM) i5-4300U CPU @ 1.90GHz (4 x 2494)
GPU Status 2d_canvas: enabled
checker_imaging: disabled_off
flash_3d: enabled
flash_stage3d: enabled
flash_stage3d_baseline: enabled
gpu_compositing: enabled
multiple_raster_threads: enabled_on
native_gpu_memory_buffers: disabled_software
rasterization: enabled
surface_synchronization: enabled_on
video_decode: enabled
webgl: enabled
webgl2: enabled
Memory (System) 7.91GB (5.45GB free)
Process Argv
Screen Reader no
VM 0%
@ghost ghost added the triage-needed Needs assignment to the proper sub-team label Feb 13, 2019
@DonJayamanne DonJayamanne changed the title Error in Python Extension Debugging failing when stoponentry=true Feb 14, 2019
@DonJayamanne
Copy link

Dup of #4223

@ghost ghost removed the triage-needed Needs assignment to the proper sub-team label Feb 14, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Mar 14, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants