eaw/Main_MiSTer
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Fix memory corruption when using new config file with long kickstart path. (#503)

Browse Source
This commit is contained in:
Matt Hargett
2022-01-06 03:24:59 -08:00
committed by GitHub
parent b56604a201
commit dac90bba4b
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
support/minimig/minimig_config.cpp
View File

@@ -378,7 +378,7 @@ static void ApplyConfiguration(char reloadkickstart)
spi_uio_cmd8(UIO_MM2_RST, rstval);
if (!UploadKickstart(minimig_config.kickstart))
{
snprintf(minimig_config.kickstart, 1024, "%s/%s", HomeDir(), "KICK.ROM");
snprintf(minimig_config.kickstart, sizeof(minimig_config.kickstart) - 1, "%s/%s", HomeDir(), "KICK.ROM");
if (!UploadKickstart(minimig_config.kickstart))
{
strcpy(minimig_config.kickstart, "KICK.ROM");
@@ -483,7 +483,7 @@ int minimig_cfg_load(int num)
// set default configuration
memset((void*)&minimig_config, 0, sizeof(minimig_config)); // Finally found default config bug - params were reversed!
memcpy(minimig_config.id, config_id, sizeof(minimig_config.id));
snprintf(minimig_config.kickstart, 1024, "%s/%s", HomeDir(), "KICK.ROM");
snprintf(minimig_config.kickstart, sizeof(minimig_config.kickstart) - 1, "%s/%s", HomeDir(), "KICK.ROM");
minimig_config.memory = 0x11;
minimig_config.cpu = 0;
minimig_config.chipset = 0;