17 Jun, 2009, Terraco wrote in the 1st comment:
Votes: 0
Every time a player tries to make a new pfile my mud gose down. I am not sure why. I am using a ROM 2.4 B6. I am also suffering from IMC errors and there are a ton of them.
17 Jun, 2009, Banner wrote in the 2nd comment:
Votes: 0
We'll need a gdb log. Usually, you go to your area directory and type:

gdb ../src/mudexecname
run port#


Then go make it crash and post the contents of bt.

Edit to fix code tag.
17 Jun, 2009, Terraco wrote in the 3rd comment:
Votes: 0
Wed Jun 17 20:43:37 2009 :: Sock.sinaddr: 174.23.25.23
Wed Jun 17 20:44:13 2009 :: Rumor@174-23-25-23.slkc.qwest.net new player.
Wed Jun 17 20:44:21 2009 :: [*****] BUG: Create_object: NULL pObjIndex.
thats what the logs are putting out.
once you get to the point when your entering the game after the MOTD it crashes
your welcome to see what I mean byt trying to connect. Loohosting.com port 6666
17 Jun, 2009, Davion wrote in the 4th comment:
Votes: 0
That's an IMC error? Looks to me like you've deleted one of the stock items loaded upon character creation.
17 Jun, 2009, Terraco wrote in the 5th comment:
Votes: 0
the IMC error is just a big mess. I dont know why its messing up. But I want to solve my new player cration prob. I know it has nothing to do with IMC.c but I thought I would mention it.
17 Jun, 2009, Davion wrote in the 6th comment:
Votes: 0
The error you're showing us tells us that you're trying to load an object who's vnum no longer exists.
17 Jun, 2009, Terraco wrote in the 7th comment:
Votes: 0
okay. So where do I find the issues to fix it. I would like to get new players able to log in lol
17 Jun, 2009, Davion wrote in the 8th comment:
Votes: 0
You have to find out which VNUM it is specifically. The best way to do this is to find the place where this error is being reported, and have it also print out the vnum in question. Honestly, it should do this already, but I guess people over looked this when developing ROM :). This is definitely in the create_object function. Look for a line that prints out this message (likely, bug("create_object: null pObjIndex",0);) and change it so it prints out the vnum in question.
17 Jun, 2009, Banner wrote in the 9th comment:
Votes: 0
Davion said:
You have to find out which VNUM it is specifically. The best way to do this is to find the place where this error is being reported, and have it also print out the vnum in question. Honestly, it should do this already, but I guess people over looked this when developing ROM :). This is definitely in the create_object function. Look for a line that prints out this message (likely, bug("create_object: null pObjIndex",0);) and change it so it prints out the vnum in question.


Change it to:

bug("obj %d: create_object: null pObjIndex",obj->vnum );
18 Jun, 2009, Zeno wrote in the 10th comment:
Votes: 0
Banner, if the obj is null how is it suppose to print obj->vnum?
18 Jun, 2009, Terraco wrote in the 11th comment:
Votes: 0
Thanx people. Got it all fixed.
18 Jun, 2009, Banner wrote in the 12th comment:
Votes: 0
Zeno said:
Banner, if the obj is null how is it suppose to print obj->vnum?

Ask Davion.
18 Jun, 2009, Zeno wrote in the 13th comment:
Votes: 0
Davion didn't say anything about obj->vnum. The vnum is most likely stored in a local var which is what should be printed out.
18 Jun, 2009, Omega wrote in the 14th comment:
Votes: 0
I posted a snippet to report issue's like this.

Years ago….


Snippet

Only thing it required once you added it, was to add a call to the vnum to each individual time create_object is called.

it reports file, function, line, and the mission vnum.

so: save.c, fread_char, 834, 2055

Very important stuff to know when debugging.
0.0/14