Debugger 'saveconfig' wasn't taking pathname of ROMs into account; it always

used the current directory.

Fixed error in generating directive lists; there sometimes were 'holes' 
at the boundary of CODE <=> DATA transitions.


git-svn-id: svn://svn.code.sf.net/p/stella/code/trunk@2129 8b62c5a3-ac7e-4cc8-8f21-d9a121418aba
This commit is contained in:
stephena 2010-09-11 14:26:21 +00:00
parent aba64fa8e4
commit cb7b93f8d1
1 changed files with 4 additions and 4 deletions

View File

@ -799,7 +799,8 @@ string CartDebug::saveConfigFile(string file)
//
// In either case, we're using the properties entry, since even ROMs that
// don't have a proper entry have a temporary one inserted by OSystem
node = FilesystemNode(name + ".cfg");
node = FilesystemNode(FilesystemNode(
myOSystem.romFile()).getParent().getPath() + name + ".cfg");
}
if(!node.isDirectory())
@ -973,11 +974,10 @@ void CartDebug::getBankDirectives(ostream& buf, BankInfo& info) const
continue;
else if(tag.type != type) // new range has started
{
// If switching from a data range, make sure the endpoint is valid
// If switching data ranges, make sure the endpoint is valid
// This is necessary because DATA sections don't always generate
// consecutive numbers/addresses for the range
if(type == CartDebug::DATA)
last = tag.address - 1;
last = tag.address - 1;
disasmTypeAsString(buf, type);
buf << " " << HEX4 << start << " " << HEX4 << last << endl;