Skip to content

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

Closed

Description

From johns (@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

sb8ywp 3

  • 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

Activity

  1. DonJayamanne commented on Nov 14, 2017

    @DonJayamanne
    Author

    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.

  2. DonJayamanne commented on Nov 14, 2017

    @DonJayamanne
    Author

    From johns (@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.

  3. DonJayamanne commented on Nov 14, 2017

    @DonJayamanne
    Author

    From johns (@jhsterling) on October 26, 2017 1:14

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

  4. DonJayamanne commented on Nov 14, 2017

    @DonJayamanne
    Author

    From Jason Adams (@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
    
  5. DonJayamanne commented on Jan 18, 2018

    @DonJayamanne
    Author

    johns (@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.

  6. 7 remaining items

  7. DonJayamanne commented on Mar 8, 2018

    @DonJayamanne
    Author

    johns (@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/

  8. goranpetrovikj commented on Apr 25, 2018

    @goranpetrovikj

    Don Jayamanne (@DonJayamanne) The experimental debugger works!

  9. DonJayamanne commented on Sep 27, 2018

    @DonJayamanne
    Author

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

  10. locked as resolved and limited conversation to collaborators on Oct 25, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    area-debuggingbugIssue identified by VS Code Team member as probable bug

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions