Pages:<< prev 1 next >>
#1 Mar 4, 2018 3:31 pm
Last edited Mar 4, 2018 3:42 pm by Vladaar
Apprentice
GroupMembers
Posts57
JoinedNov 24, 2016
Good Afternoon,
I expect most people don't try this, but I did it out of curiosity because I found that I could not get it to run on my game as well.
Anyone tried running smaugfuss with gdb command? The results are lots of errors due to file loading.
I searched google and what I am getting is these are errors that gcc won't report, but are actual errors?
gdb smaugfuss19/src/smaug
Reading symbols from smaugfuss19/src/smaug...done.
(gdb) run 4100
Starting program: /home/vladaar/Downloads/smaugfuss19/src/smaug 4100
Sun Mar 4 16:26:13 2018 :: Booting Database
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
Sun Mar 4 16:26:13 2018 :: [*****] BOOT: ---------------------[ Boot Log ]--------------------
Sun Mar 4 16:26:13 2018 :: Initializing libdl support...
Sun Mar 4 16:26:13 2018 :: Loading commands...
Sun Mar 4 16:26:13 2018 :: [*****] BUG: Cannot open ../system/commands.dat
[Inferior 1 (process 18598) exited normally]
(gdb)
Anyway, maybe something not to worry about or yes? Obviously game will run fine as-is.
Smaugfuss error is more vague than what mine was.
Mine points too
Sun Mar 4 14:25:51 2018 :: [*****] BUG: __FileOpen: can't open system/bug.txt for a. Called from db.c:5056
Maybe gdb just has a problem with fp being used in that way as in there is a correct standardized format we are supposed to use now?
I expect most people don't try this, but I did it out of curiosity because I found that I could not get it to run on my game as well.
Anyone tried running smaugfuss with gdb command? The results are lots of errors due to file loading.
I searched google and what I am getting is these are errors that gcc won't report, but are actual errors?
gdb smaugfuss19/src/smaug
Reading symbols from smaugfuss19/src/smaug...done.
(gdb) run 4100
Starting program: /home/vladaar/Downloads/smaugfuss19/src/smaug 4100
Sun Mar 4 16:26:13 2018 :: Booting Database
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
Sun Mar 4 16:26:13 2018 :: [*****] BOOT: ---------------------[ Boot Log ]--------------------
Sun Mar 4 16:26:13 2018 :: Initializing libdl support...
Sun Mar 4 16:26:13 2018 :: Loading commands...
Sun Mar 4 16:26:13 2018 :: [*****] BUG: Cannot open ../system/commands.dat
[Inferior 1 (process 18598) exited normally]
(gdb)
Anyway, maybe something not to worry about or yes? Obviously game will run fine as-is.
Smaugfuss error is more vague than what mine was.
Mine points too
Sun Mar 4 14:25:51 2018 :: [*****] BUG: __FileOpen: can't open system/bug.txt for a. Called from db.c:5056
if((fp = FileOpen(BUG_FILE, "r" ))) // gdb shows this is a bug { fprintf(fp, "%s &D\n", buf); FileClose(fp); fp = NULL; }
Maybe gdb just has a problem with fp being used in that way as in there is a correct standardized format we are supposed to use now?
#2 Mar 4, 2018 4:23 pm
Last edited Mar 4, 2018 4:23 pm by Vladaar
Apprentice
GroupMembers
Posts57
JoinedNov 24, 2016
I tried changing mine to a+ to see if that would get rid of the error and allow gdb to run the game.
if((fp = FileOpen(BUG_FILE, "a+" ))) // gdb shows this is a bug
Sun Mar 4 17:21:59 2018 :: [*****] BUG: __FileOpen: can't open system/bugs.dat for a+. Called from db.c:5056
Sun Mar 4 17:21:59 2018 :: [*****] BUG: __FileOpen: can't open system/bugs.dat for a+. Called from db.c:5056
Sun Mar 4 17:21:59 2018 :: [*****] BUG: __FileOpen: can't open system/bugs.dat for a+. Called from db.c:5056
Program received signal SIGSEGV, Segmentation fault.
_IO_vfprintf_internal (s=0x7fffff7ff540, format=0x63c596 "%s :: %s\n", ap=0x7fffff801bf8) at vfprintf.c:1312
1312 vfprintf.c: No such file or directory.
(gdb) quit
Nope same bugs with the loading of the files.
if((fp = FileOpen(BUG_FILE, "a+" ))) // gdb shows this is a bug
Sun Mar 4 17:21:59 2018 :: [*****] BUG: __FileOpen: can't open system/bugs.dat for a+. Called from db.c:5056
Sun Mar 4 17:21:59 2018 :: [*****] BUG: __FileOpen: can't open system/bugs.dat for a+. Called from db.c:5056
Sun Mar 4 17:21:59 2018 :: [*****] BUG: __FileOpen: can't open system/bugs.dat for a+. Called from db.c:5056
Program received signal SIGSEGV, Segmentation fault.
_IO_vfprintf_internal (s=0x7fffff7ff540, format=0x63c596 "%s :: %s\n", ap=0x7fffff801bf8) at vfprintf.c:1312
1312 vfprintf.c: No such file or directory.
(gdb) quit
Nope same bugs with the loading of the files.
#3 Mar 7, 2018 5:04 pm
Geomancer
GroupAdministrators
Posts1,914
JoinedJul 26, 2005
to run smaug in gdb (i do it lots with lop and use to with normal smaug) be in src folder and type
gdb smaug
cd ../area
run
Should work just fine Granted it has been ages.
gdb smaug
cd ../area
run
Should work just fine Granted it has been ages.
#4 Mar 7, 2018 8:51 pm
Apprentice
GroupMembers
Posts57
JoinedNov 24, 2016
Yeah that's the procedure, just saying there are bugs with file opening. It's not really important was just thinking maybe there is a format update we are missing that is causing it to do that.
Pages:<< prev 1 next >>