Login
User Name:

Password:



Register
Forgot your password?
Vote for Us!
tintin++ ogg sound player script for linux
Author: Robert Smith
Submitted by: Vladaar
6Dragons ogg Soundpack
Author: Vladaar
Submitted by: Vladaar
6Dragons 4.4
Author: Vladaar
Submitted by: Vladaar
LoP 1.46
Author: Remcon
Submitted by: Remcon
LOP 1.45
Author: Remcon
Submitted by: Remcon
Users Online
CommonCrawl, Bing, DotBot, Yandex, Google

Members: 0
Guests: 13
Stats
Files
Topics
Posts
Members
Newest Member
481
3,739
19,386
622
ignatius
Today's Birthdays
There are no member birthdays today.
Related Links
» SmaugMuds.org » Codebases » SmaugFUSS » Cant run smaugfuss with gdb
Forum Rules | Mark all | Recent Posts

Cant run smaugfuss with gdb
< Newer Topic :: Older Topic > loading errors

Pages:<< prev 1 next >>
Post is unread #1 Mar 4, 2018, 1:31 pm   Last edited Mar 4, 2018, 1:42 pm by Vladaar
Go to the top of the page
Go to the bottom of the page

Vladaar
Fledgling
GroupMembers
Posts44
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
  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?
       
Post is unread #2 Mar 4, 2018, 2:23 pm   Last edited Mar 4, 2018, 2:23 pm by Vladaar
Go to the top of the page
Go to the bottom of the page

Vladaar
Fledgling
GroupMembers
Posts44
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.
       
Post is unread #3 Mar 7, 2018, 3:04 pm
Go to the top of the page
Go to the bottom of the page

Remcon
Geomancer
GroupAdministrators
Posts1,874
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 <port>

Should work just fine Granted it has been ages.
       
Post is unread #4 Mar 7, 2018, 6:51 pm
Go to the top of the page
Go to the bottom of the page

Vladaar
Fledgling
GroupMembers
Posts44
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 >>