The debug process never connected back to Wing: Aborting debug session. See Trouble-shooting Failure to Debug in the product manual.

I have installed python3.7, but wing pro 6.0 tips that The debug process never connected back to Wing: Aborting debug session. See Trouble-shooting Failure to Debug in the product manual.

So I cannot debug any code. I need help,

thanks.

The first step is to make sure you have the current version of Wing 6. Earlier versions of Wing 6 did not support Python 3.7 because it did not exist yet. A way to get more information about failures like this is to Restart from the Options menu in the Python Shell tool in Wing. Or send us a bug report from Wing's Help menu with the error log included where prompted.

4.2k

Wingware Support

answered 2018-10-12 10:20:00 -0600, updated 2019-03-16 12:05:51 -0600

edit flag offensive 0 remove flag delete link

Comments

I have a similar issue here: before, I was having a 32 bit Linux OS running on a RPi and the debugger went fine. I had to change to a 64 bit OS and when trying to start the debugger, I get the following error in the Python Shell:

ImportError: Failed to find loader for 'tdbgtracer36' in '/home/ubuntu/.wingpro7/remote-7.0.2.0/src/debug/tserver/__os__/linux-x64'

Is there something special to do for 64 bit OS'es?

Best,

GeertVcm (2021-03-26 11:43:11 -0600) edit

add a comment see more comments

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account. This space is reserved only for answers. If you would like to engage in a discussion, please instead post a comment under the question or an answer that you would like to discuss.

Add Answer

The debug process never connected back to Wing: Aborting debug session. See Trouble-shooting Failure to Debug in the product manual. edit

Comments

1 Answer

Comments