Author Topic: SE stack on entering java debugger  (Read 213 times)

rjpontefract

  • Senior Community Member
  • Posts: 250
  • Hero Points: 10
SE stack on entering java debugger
« on: November 14, 2023, 10:55:29 PM »
SE 28 on Windows 10.

I hit F5 to start the Java debugger and got the following stack (paths have been trimmed):

Code: [Select]
Stack trace written to file: C:\Users\PONTEF\AppData\Local\Temp\vsstack.
 Invalid argument
mainwindow.ex 2826 mainwindow:_autorestore_from_xml(20,0)  p_window_id: 339 (invalid)
mainwindow.ex 3752 debug_switch_mode(1,0)  p_window_id: 339 (invalid)
tbview.ex 195 tbDebugSwitchMode(1,0)  p_window_id: 339 (invalid)
debug.ex 542 activate_debug(jdwp,,8000,,30,<empty>,<empty>,,go)  p_window_id: 339 (invalid)
debug.ex 1272 debug_begin(jdwp,,8000,,30,<empty>,<empty>,,go)  p_window_id: 339 (invalid)
compile.ex 10608 compile:_project_command3(7,target,0,debug,C:\WS\Development\...\verticle\WorkerVerticle.java,
   6:   verticle   7:   0
   8:   1
   9:   0
   10:   0
   11:   go
   12:   
   13:   
  p_window_id: 339 (invalid)
compile.ex 3337 _project_command(debug,C:\Development\...\verticle\WorkerVerticle.java,verticle,0,1,0,0,go,,)
  p_window_id: 339 (invalid)
compile.ex 2692 _project_command2(debug,0,1,0,0,go,C:\Development\...\verticle\WorkerVerticle.java,,)
  p_window_id: 339 (invalid)
compile.ex 2303 _project_debug2(0,go,,)  p_window_id: 339 (invalid)
debug.ex 1876 debug_go(0,,)  p_window_id: 339 (invalid)
compile.ex 1849 project_debug()  p_window_id: 339 (invalid)

The debug session started however but none of the debug windows were present.  The next start of the debugger required me to re-open the debug toolbars and tool windows.

Clark

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 6797
  • Hero Points: 525
Re: SE stack on entering java debugger
« Reply #1 on: November 14, 2023, 11:30:14 PM »
Reproduced. Should be hot fixable.

rjpontefract

  • Senior Community Member
  • Posts: 250
  • Hero Points: 10
Re: SE stack on entering java debugger
« Reply #2 on: November 14, 2023, 11:33:30 PM »
That's good to hear, thanks!