Welcome to the Builder Academy

Question Disconnected when entering the MUD

More
03 Aug 2012 14:47 - 03 Aug 2012 18:38 #514 by linkg
Two days ago I was translating some worlds in my mud to portuguese.
After the changes, I started receiving the following error in syslog.1:
Code:
Aug 3 07:33:27 :: SYSERR: Received SIGHUP, SIGINT, or SIGTERM. Shutting down ...

This error only happens as follows:
I start the mud, I create a new character and close the game.
When trying to enter again, when I type the password, my mud automatically disconnects.
(this only happens with existing characters, if I create a new one, the game opens with perfection)

Soon after I try to connect again with an existing character, the following message appears in the file syslog.CRASH:
Code:
Aug 3 08:34:12 :: (null) has connected.

Trying to figure out what the problem is, I got through the Debug Mode these lines:
Code:
I typed > gdb bin/circle lib/core.22830 Program terminated with signal 11, Segmentation fault. #0 0x005e1cc0 in strcpy () from /lib/libc.so.6 (gdb) bt #0 0x005e1cc0 in strcpy () from /lib/libc.so.6 #1 0x0806fa59 in AddRecentPlayer (chname=0x0, chhost=0xa997974 "189001131226.usr.predialnet.com.br", newplr=0 '\000', cpyplr0 '\000') at act.wizard.c:4922 #2 0x080e6082 in nanny (d=0xa997970, arg=0xbf8aa424 "linkg") at interpreter.c:1692 #3 0x0809aede in game_loop (local_mother_desc=3) at comm.c:877 #4 0x0809bfb7 in init_game (argc=0, argv=0xbf8aa9a4) at comm.c:527 #5 main (argc=0, argv=0xbf8aa9a4) at comm.c:353 (gdb) up #1 0x0806fa59 in AddRecentPlayer (chname=0x0, chhost=0xa997974 "189001131226.usr.predialnet.com.br", newplr=0 '\000', cpyplr0 '\000') at act.wizard.c:4922 4922 strcpy(this->name, chname); (gdb) up #2 0x080e6082 in nanny (d=0xa997970, arg=0xbf8aa424 "linkg") at interpreter.c:1692 1692 if (AddRecentPlayer(GET_NAME(d->character), d-host, FALSE, FALSE) == FALSE) (gdb) up #3 0x0809aede in game_loop (local_mother_desc=3) at comm.c:877 877 nanny(d, comm); (gdb) up #4 0x0809bfb7 in init_game (argc=0, argv=0xbf8aa9a4) at comm.c:527 527 game_loop(mother_desc); (gdb) up #5 main (argc=0, argv=0xbf8aa9a4) at comm.c:353 353 init_game(port); (gdb) print port $1 = 3011

Another thing that happens:
Running the mud in the command ./autorun and trying to get into some existing character, after entering the password appears as follows:
Code:
./autorun: line 174: 28643 Segmentation fault (core dumped) nohup bin/circle $FLAGS $PORT >>syslog 2>&1

Well, I never changed or added new codes in my tbamud. I use version 3.63 with all modifications of existing mudSVN. My tbamud is like the original, only translated into another language. I could not understand why this error appeared.

If anyone can help I will be grateful!
Last edit: 03 Aug 2012 18:38 by linkg.

Please Log in or Create an account to join the conversation.

More
03 Aug 2012 17:55 - 03 Aug 2012 17:55 #515 by Halenbane
Not knowing what changes you made it may be a bit more difficult to diagnose it. Is there any way you can give us an idea of the code changes you made before the error started? I know you said it was stock TBA but what did you do in regards to the language?
Last edit: 03 Aug 2012 17:55 by Halenbane.

Please Log in or Create an account to join the conversation.

More
03 Aug 2012 18:26 #516 by linkg
The changes were only in words like:
1 - directions north/south/east/west.
2 - Name, title, sex and class.
3 - Attribute Str, Con, Int, Charm... And all other words related to player characters.
4 - Some commands such as: kill, look, buy, sell, inventory, equipment and more in the interpreter.c.

I was translated, without error, all of this worlds when I run the make file, but I believe the problem is in the players.c, even if nothing point to this file. Because there is a place that interferes directly in the loading and saving of the characters, attributes and passwords.

If the GDB gave me a hint more directly I would have solved the problem, however the way It shows me the error does not help. :(

Please Log in or Create an account to join the conversation.

More
03 Aug 2012 18:29 #517 by Halenbane
The reason I ask is because I have seen SIGHUP/SIGINT/SIGTERM issues even from a small typo somewhere. A missing }, extra &, whatever. The place I would recommend starting is carefully checking over your changes for typos. I know this seems obvious, but sometimes after searching for an error for hours I will eventually find a small typo that I had previously overlooked.

Please Log in or Create an account to join the conversation.

More
03 Aug 2012 18:33 #518 by linkg
Understood, I'll take a look.

Please Log in or Create an account to join the conversation.

More
03 Aug 2012 18:44 - 03 Aug 2012 18:48 #519 by linkg
I'm realizing that maybe tbamud does not recognize special characters such as ã, õ, ç, á, ó, í, ê, é.
Is this the problem? If so, how to solve this?
Last edit: 03 Aug 2012 18:48 by linkg.

Please Log in or Create an account to join the conversation.

Time to create page: 0.190 seconds