When you invoke bildb with --bildb-init=foo.yml, if foo.yml specifies some locations that aren't initialized by Primus, bildb silently ignores those locations. What it should do is first allocate those locations, then set them to the value specified by foo.yml.
During an interactive debugging session, if you type set 0xADDR=0xVALUE, if 0xADDR isn't allocated, then bildb will allocate it, and then set it to 0xVALUE. We can just copy this same idea over to the initialization from an init file.
When you invoke
bildbwith--bildb-init=foo.yml, iffoo.ymlspecifies some locations that aren't initialized by Primus,bildbsilently ignores those locations. What it should do is first allocate those locations, then set them to the value specified byfoo.yml.During an interactive debugging session, if you type
set 0xADDR=0xVALUE, if0xADDRisn't allocated, thenbildbwill allocate it, and then set it to0xVALUE. We can just copy this same idea over to the initialization from an init file.