Opened 6 days ago

#439 new defect

If use use the BCE "get_flagbox" (gfb) command with 0 as the argument, it crashes

Reported by: Eric Swenson Owned by: Eric Swenson
Priority: minor Milestone:
Component: Hardcore Version: MR12.9
Keywords: Cc:

Description

The "gfb 0" command (not legal) results in:

bce (boot) 1303.4: M-> gfb 0

CONSOLE: ALERT
1303.5  initial_error_handler: out_of_bounds condition by 451|14024 referencing 5|616220; MC at 62|3320.
1303.5  Multics not in operation; control process: Initializer.SysDaemon.z.
2103.6  initializer: 6009  scas_init  state 1  phase 6.
2103.6  initializer: 6010  tc_init$early  state 1  phase 6.
2103.6  initializer: 6011  init_sst$early  state 1  phase 6.
2103.6  initializer: 6012  disabling slt allocation  state 1  phase 6.
2103.6  initializer: 6013  initialize_faults$interrupt_init  state 1  phase 6.
2103.6  initializer: 6016  load_disk_mpcs  state 1  phase 6.
2103.6  initializer: 6017  init_pvt  state 1  phase 6.
2103.6  initializer: 6018  read_disk$init  state 1  phase 6.
2103.6  initializer: 6019  init_root_vols  state 1  phase 6.
2103.6  initializer: 6020  establish_temp_segs  state 1  phase 6.
2103.6  initializer: 6021  find_file_partition  state 1  phase 6.
2103.6  initializer: 6025  load_mst$init_commands  state 1  phase 6.
2103.6  initializer: 6028  scs_and_clock_init$date_time  state 1  phase 6.
1303.6  initializer: 6029  io_config_init  state 1  phase 6.
1303.6  initializer: 6030  ioi_init  state 1  phase 6.
1303.6  initializer: 6032  bce_get_to_command_level  state 1  phase 6.
bce (bce_crash) 1303.6:

Change History (0)

Note: See TracTickets for help on using tickets.