Single step does not work on centos 7 w/ 32bit python

[DonJayamanne]

From @jhsterling on October 24, 2017 17:18

Environment data

VS Code version: 1.17.2
Python Extension version: 0.7.0
Python Version: 2.7.13 :: Anaconda, Inc.
OS and version: CentOS Linux release 7.1.1503 (Core)

Actual behavior

When debugging if F10 or single step is pressed the debug session is lost

Expected behavior

single step

Steps to reproduce:

• Start a debug session with stop on entry == true
• press F10

• Pressing break causes nothing to occur
• Pressing stop ends the debug session
• All others are grayed out
• works with 64 bit python

Logs

Output from Python output panel

Output from Console window (Help->Developer Tools menu)

Copied from original issue: DonJayamanne/pythonVSCode#1338

[DonJayamanne]

works with 64 bit python

If this is the case, then under what config doesn't it work. I assume it doesn't work in 32bit python.

[DonJayamanne]

From @jhsterling on October 26, 2017 0:39

Right it does not work in 32bit python on Centos 7. I will try it on Ubuntu tonight.

[DonJayamanne]

From @jhsterling on October 26, 2017 1:14

Same behavior on Ubuntu. Using a debugger (pdb i assume) via ipython works correctly.

[DonJayamanne]

From @ancillaryCode on November 7, 2017 18:22

I get the same issue on Debian 32 bit. When I run strace on the Python process, it's waiting on a futex.

$ strace -p 3906
strace: Process 3906 attached
futex(0xc5df40, FUTEX_WAIT_BITSET_PRIVATE|FUTEX_CLOCK_REALTIME, 1, NULL, 0xffffffff

[DonJayamanne]

@jhsterling Please could you confirm you're using Ubuntu 32bit.
I'd like to confirm that everyone having this issue is using a 32bit Linux OS.

[jhsterling]

Don, I am using 64 bit Linux installations. 1- Centos 7 and 2-Mint 18.2. We develop for 32 bit embedded processors. Our simulation uses a 32 bit python front end.

…

-John

On Jan 18, 2018, at 3:39 PM, Don Jayamanne ***@***.***> wrote: @jhsterling <https://github.com/jhsterling> Please could you confirm you're using Ubuntu 32bit. I'd like to confirm that everyone having this issue is using a 32bit Linux OS. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#206 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AHwSeKr_dzsc9XPXgK_Zqv58GYLszypcks5tL8gagaJpZM4Qdpw4>.

[jhsterling]

This is my current toolset
Linux lmt-fwdev-52 4.2.3-1.el7.elrepo.x86_64 #1 SMP Sat Oct 3 10:19:41 EDT 2015 x86_64 x86_64 x86_64 GNU/Linux
Python 2.7.13 :: Anaconda custom (32-bit)
gcc version 4.8.3 20140911 (Red Hat 4.8.3-9) (GCC)
code 1.19.2 490ef761b76b3f3b3832eff7a588aac891e5fe80 x64

[goranpetrovikj]

I have the same issue on Ubuntu 32bit.

VS Code Version 1.20.0
Commit c63189deaa8e620f650cc28792b8f5f3363f2c5b
Date 2018-02-07T17:11:23.959Z
Shell 1.7.9
Renderer 58.0.3029.110
Node 7.9.0
Architecture ia32

Python Extension Version: 2018.1 (01 Feb 2018)

[DonJayamanne]

@jhsterling @goranpetrovikj
Please could you try our experimental debugger. You can find further information on this here:
https://blogs.msdn.microsoft.com/pythonengineering/2018/03/08/python-in-visual-studio-code-feb-2018-release/

[goranpetrovikj]

@DonJayamanne The experimental debugger works!

[DonJayamanne]

Closing as the experimental debugger resolves this issue and the experimental debugger is the default.