Gopher2600/debugger/halt_breakpoints_test.go
JetSetIlly d788fb46bb break/trap targets are now aware of CPU instruction boundaries
halting conditions are checked every video-cycle. this reverts a
temporary change made in a73dcae6dcc61e4ced03f23fe4df504cb966fb36

renamed files in debugger package for clarity
2021-10-07 15:40:34 +01:00

57 lines
2 KiB
Go

// This file is part of Gopher2600.
//
// Gopher2600 is free software: you can redistribute it and/or modify
// it under the terms of the GNU General Public License as published by
// the Free Software Foundation, either version 3 of the License, or
// (at your option) any later version.
//
// Gopher2600 is distributed in the hope that it will be useful,
// but WITHOUT ANY WARRANTY; without even the implied warranty of
// MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
// GNU General Public License for more details.
//
// You should have received a copy of the GNU General Public License
// along with Gopher2600. If not, see <https://www.gnu.org/licenses/>.
package debugger_test
func (trm *mockTerm) testBreakpoints() {
// debugger starts off with no breakpoints
trm.sndInput("LIST BREAKS")
trm.cmpOutput("no breakpoints")
// add a break. this should be successful so there should be no feedback
trm.sndInput("BREAK SL 100")
trm.cmpOutput("")
// list breaks and check last line of output
trm.sndInput("LIST BREAKS")
trm.cmpOutput(" 0: Scanline->100")
// try to add same break. check error feedback
trm.sndInput("BREAK SL 100")
trm.cmpOutput("already exists (Scanline->100)")
// add multi-condition break
trm.sndInput("BREAK SL 100 & CL 100")
trm.cmpOutput("")
// check last line of list breaks. we've already added a break so this new
// break should be number "1" (rather than number "0")
trm.sndInput("LIST BREAKS")
trm.cmpOutput(" 1: Scanline->100 & Clock->100")
// try to add exactly the same breakpoint. expect failure
trm.sndInput("BREAK SL 100 & CL 100")
trm.cmpOutput("already exists (Scanline->100 & Clock->100)")
// the following break is logically the same as the previous break but
// expressed differently. the debugger should not add it even though the
// expression is not exactly the same.
trm.sndInput("BREAK CL 100 & SL 100")
trm.cmpOutput("already exists (Scanline->100 & Clock->100)")
trm.sndInput("BREAK CL 100")
trm.cmpOutput("")
}