complete noob with swr2.0 compilation problem

Posted by Achan on Wed 30 Aug 2006 03:30 AM — 15 posts, 42,230 views.

#0
I never tried to set up a mud before, coded a little from time to time but never did anything like this. Anyway after looking through this forum I got answers to a lot of problems I had.

I'm running SWR 2.0 and I have no 'startup' file anywhere. I have a run-swr which, when I tried to run, gives me a "permission denied".
I do have a "swr" file though, in the swr/bin directory (which appears in green and has a * after it when I type ls). I copied it to the src directory also.

So I go to the area directory and type

"../src/swr 1234 &"

or

"nohup ../src/swr 1234 &" and then it almost works, it gives me this:

Wed Aug 30 13:08:40 2006 :: Loading socials
Wed Aug 30 13:08:40 2006 :: Loading skill table
Wed Aug 30 13:08:40 2006 :: Sorting skill table...
Wed Aug 30 13:08:40 2006 :: Initializing request pipe
Wed Aug 30 13:08:40 2006 :: Initializing random number generator
Wed Aug 30 13:08:40 2006 :: Setting time and weather
Wed Aug 30 13:08:40 2006 :: Assigning gsn's
Wed Aug 30 13:08:40 2006 :: Reading in area files...
(help.are)
limbo
mobiles
objects
Wed Aug 30 13:08:40 2006 :: Fixing exits
Wed Aug 30 13:08:40 2006 :: Loading boards
Wed Aug 30 13:08:40 2006 :: ../boards/mail
Wed Aug 30 13:08:40 2006 :: ../boards/gnet
Wed Aug 30 13:08:40 2006 :: Loading clans
Wed Aug 30 13:08:40 2006 :: Loading clans...
Wed Aug 30 13:08:40 2006 :: $
Wed Aug 30 13:08:40 2006 :: Done clans

Wed Aug 30 13:08:40 2006 :: Loading bans
Wed Aug 30 13:08:40 2006 :: Loading corpses

This is so far the best I ever got it to work. After those, it waits until I hit return and then it produces a core dump.

[1]+ Segmentation fault (core dumped) nohup ../src/swr 1234

The SWR 2.0 I downloaded comes with almost nothing and I think that's the main problem (there are no areas other than the bare necessities, which are limbo, an .o.are area which mostly contains empty voids, and some helpfiles).

There's no players directory (and no gods directory either) and I think that is why it dies on the 'Loading corpses' part... anyways, that's all I know about my problem, any advice?

I'm not running it with Cygwin, I'm running it on a real server. It's Linux I think, again, I'm a noob and don't know much.
Amended on Wed 30 Aug 2006 03:37 AM by Achan
USA #1
Looks like it crashed. Use gdb to debug it, see the gdb guide Nick made for details.
#2
Thanks, but I don't understand the guide hehe.

I tried typing "gdb (path) core####.core", it says gdb: command not found.

Maybe I have the wrong OS. In the guide all the prompt lines end with $ and in the shell, all the prompt lines end with #. Does that mean anything important?
USA #3
Try using uname to check what you're using.
#4
Linux.

(I love your quick responses, Zeno!)
USA #5
Maybe you don't have gdb, which would seem sort of odd. Try typing man gdb.
#6
man gdb
man: No such file or directory
Failed to open the message catalog man on the path NLSPATH=<none>

No manual entry for gdb
USA #7
Looks like you don't have gdb. I'd say do a whereis, but I think it's certain you don't have it. Talk to your host, you're missing something very helpful.
#8
whereis
whereis [ -sbmu ] [ -SBM dir ... -f ] name...

So I do have it.. only no clue how to use it.
USA #9
whereis gdb
#10
]# whereis gdb
gdb:

That's what it gives me.. "gdb: "
{and nothing}.
USA #11
Right, so gdb is not installed.

You'll have to talk to your host.
#12
Alright, thanks.

So no guesses without the GDB debugging on what's wrong?
Australia Forum Administrator #13
Without all the appropriate directories it is probably opening a file (or directory), getting a NULL pointer as a result (0), not checking it (that is, assuming the file/directory exists) and then using the null pointer.

Exactly which directory/file gdb would tell you, however I recommend setting up the standard files for swr, to minimize the likelihood of this happening.
USA #14
How did you unzip your swr directory? Did you do it on your Windows box and then upload it? That might be your problem, since Winzip doesn't create empty directories, but almost all Linux tools do.