Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. Qt for Python
  4. PyCharm debug failure with shiboken6 6.2.3-3
Forum Updated to NodeBB v4.3 + New Features

PyCharm debug failure with shiboken6 6.2.3-3

Scheduled Pinned Locked Moved Solved Qt for Python
3 Posts 2 Posters 1.0k Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • S Offline
    S Offline
    StarterKit
    wrote on last edited by
    #1

    Hi all,
    I recently upgraded shiboken6 from 6.2.3-2 to 6.2.3-3. I can run my application normally but it fails if I try to execute "Debug" in PyCharm:

    /usr/bin/python /usr/share/pycharm/plugins/python-ce/helpers/pydev/pydevd.py --multiproc --qt-support=auto --client 127.0.0.1 --port 40109 --file /path-to/my-app.py
    Connected to pydev debugger (build 213.6777.50)
    python: /usr/src/debug/pyside-setup-opensource-src-6.2.3/sources/shiboken6/libshiboken/signature/signature_helper.cpp:103: int add_more_getsets(PyTypeObject*, PyGetSetDef*, PyObject**): Assertion `false' failed.
    
    Process finished with exit code 134 (interrupted by signal 6: SIGABRT)
    

    I have pyside6 6.2.3-3 installed. Everything works with previous version shiboken6 6.2.3-2.
    The question is - should I wait for pyside6 update or this is some kind of a bug? What do you think?

    1 Reply Last reply
    0
    • S Offline
      S Offline
      Szczempus
      wrote on last edited by
      #2

      I had simmilar problem. For me changing setting in debugin options File->Settings-> Build, Execution , Deployment -> Python Debbuger and in PyQt compatible changing from dropdown options to PySide worked.

      S 1 Reply Last reply
      0
      • S Szczempus

        I had simmilar problem. For me changing setting in debugin options File->Settings-> Build, Execution , Deployment -> Python Debbuger and in PyQt compatible changing from dropdown options to PySide worked.

        S Offline
        S Offline
        StarterKit
        wrote on last edited by StarterKit
        #3

        @Szczempus, thanks for your comment. Yes, I had Auto in a setting you mentioned. I changed it to PySide2 and it didn't work either. With PySide it works, as you said.
        It sounds like a small bug of PyCharm as we use PySide6. Do you know how to report it to JetBrains?

        P.S. The same error persists with version 6.2.4.

        1 Reply Last reply
        0

        • Login

        • Login or register to search.
        • First post
          Last post
        0
        • Categories
        • Recent
        • Tags
        • Popular
        • Users
        • Groups
        • Search
        • Get Qt Extensions
        • Unsolved