VMS.DevelopDebug History

Hide minor edits - Show changes to output - Cancel

Changed lines 1-2 from:
!!Random debugging notes, waiting to be organized ; )
When debugging, you might find it helpful to put breakpoints inside "VMS__primitives_asm.s" on a random assembly instruction in the "switchToSlv" and so on.. so you can track all
the transitions between slave, coreCtlr, and master..
to:
!!Tips on debugging

!!!Sequential Mode
The most useful debugging feature is the sequential mode, which turns on a deterministic scheduling sequence, and schedules all work to the same core. Hence, one can single-step through the entire application, including calls into VMS,
the plugin functions, request handlers, and so on.

!!!Useful Breakpoint Locations
When debugging, you might find it helpful to put breakpoints inside "VMS__primitives_asm
.s", which is in the VMS directory for hardware primitives. By putting breakpoints on the assembly primitives used to switch among slave, core controller, and the master, you get a break every time the application suspends and switches over to the runtime. The breakpoint can just be placed on a random assembly instruction in the "switchToSlv" and so on.. pick which transitions among slave, coreCtlr, and master you want to track. This is especially convenient when used in combination with sequential mode.
September 10, 2012, at 05:17 AM by 24.130.186.152 -
September 10, 2012, at 05:17 AM by 24.130.186.152 -
Deleted lines 2-3:

In Netbeans, to debug a program, have to right-click on the project name in project tab, choose "properties" then the Run bullet. This brings up a dialog. In it, choose the directory to run from, and then set the command-line in the top field, with any paths being relative to the chosen run directory
July 05, 2012, at 07:32 AM by 24.130.186.152 -
Changed lines 1-2 from:
!!Random notes, waiting to be organized ; )
to:
!!Random debugging notes, waiting to be organized ; )
July 05, 2012, at 07:31 AM by 24.130.186.152 -
Deleted line 1:
Changed lines 3-5 from:
When debugging, you might find it helpful to put breakpoints inside "VMS__primitives_asm.s" on a random assembly instruction in the "switchToSlv" and so on.. so you can track all the transitions between slave, coreCtlr, and master..
to:
When debugging, you might find it helpful to put breakpoints inside "VMS__primitives_asm.s" on a random assembly instruction in the "switchToSlv" and so on.. so you can track all the transitions between slave, coreCtlr, and master..

In Netbeans, to debug a program, have to right-click on the project name in project tab, choose "properties" then the Run bullet. This brings up a dialog. In it, choose the directory to run from, and then set the command-line in the top field, with any paths being relative to the chosen run directory
July 05, 2012, at 07:28 AM by 24.130.186.152 -
Added lines 1-4:


!!Random notes, waiting to be organized ; )
When debugging, you might find it helpful to put breakpoints inside "VMS__primitives_asm.s" on a random assembly instruction in the "switchToSlv" and so on.. so you can track all the transitions between slave, coreCtlr, and master..