Author Topic: Beta2: java junit debug vsstack  (Read 451 times)

Marcel

  • Senior Community Member
  • Posts: 132
  • Hero Points: 8
Beta2: java junit debug vsstack
« on: September 03, 2014, 03:24:02 am »
Running a unit test in debug mode yields a stack trace and the loss of the main tools group (need to tbresetall):

 Slick-C STACK TRACE ******************************
 Created on 9/2/2014 at 21:19:56 (157 ms)
 SlickEdit Version 19.0.0.5 Copyright 1988-2014 SlickEdit Inc.
 Edit module and type "st -f <offset>" to get the
 run-time error position

 error code=-3015
 Invalid argument

mainwindow.ex 2136 mainwindow:_autorestore_from_view(15,0)   p_window_id: 69   p_object: OI_EDITOR   p_name:
mainwindow.ex 3066 debug_switch_mode(0,0)   p_window_id: 69   p_object: OI_EDITOR   p_name:
tbview.ex 305 tbDebugSwitchMode(0,0)   p_window_id: 69   p_object: OI_EDITOR   p_name:
debug.ex 851 debug_maybe_stop_debugging()   p_window_id: 69   p_object: OI_EDITOR   p_name:
debug.ex 9482 debug_stop(1,0)   p_window_id: 69   p_object: OI_EDITOR   p_name:
debug.ex 23377 debug:debug_session_update_debugger(1,vm_stop,8,0,,0,0,0,0,0,1,1,0,0,0)   p_window_id: 69   p_object: OI_EDITOR   p_name:
debug.ex 25627 _UpdateDebugger(0)   p_window_id: 69   p_object: OI_EDITOR   p_name:
autosave.ex 555 _as_callback()   p_window_id: 69   p_object: OI_EDITOR   p_name:

Lee

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 993
  • Hero Points: 84
Re: Beta2: java junit debug vsstack
« Reply #1 on: September 03, 2014, 12:21:29 pm »
Did this keep occurring after tbresetall or just the one time thing?

Marcel

  • Senior Community Member
  • Posts: 132
  • Hero Points: 8
Re: Beta2: java junit debug vsstack
« Reply #2 on: September 03, 2014, 01:19:39 pm »
In some projects it happens consistently, in others intermittently.
I am attaching a sample project which has a good chance of reproducing the problem. Ignore the squirly directory structure, I needed it to repro another bug.

Build the project, then unit test debug the two test classes individually (Project right-click->debug). Hit f5 when you reach the initial breakpoint. You may have to repeat this a few times. I see a number of different reactions:
  • The vsstack as described
  • A recursion too deep stack dump
  • The debugger never finishes after hitting f5