I am new to Slickedit (using 18.0.1). I love it but the debugger is painfully slow (on my setup). The app I am trying to debug is multi-threaded, with more than 100 threads. Once I attach to the running process, any action takes a long time (7-8 seconds), including each time I step to next line. I enabled gdb output via the def-debug-logging macro variable and found out that every step-next command also issues a "-thread-info" command. This command always takes a very long time (6-7 seconds), hence the slow performance. Why does Slickedit need to call -thread-info every time? Is this a bug? Is there any way to disable this or use a more efficient command to retrieve thread info? Or maybe I set an option I shouldn't have set?
Thanks for your help!