Strange Crash

[OscarGrouch05]

that is a ref to what andmetal said above on 1-16-2010
What's up with the nulls in the characters' names?

[KingMort]

Wow still getting these , and Now i know for sure it is BOT related, which on my end they are called GOONS but all i did was change the #bot commands and descriptions to #goon didn't mess with anything else... anyway here is the most recent crash which was just after giving the player his new goon from my RA promo...

Core was generated by `./zone'.
Program terminated with signal 11, Segmentation fault.
[New process 26798]
[New process 26804]
[New process 26803]
[New process 26802]
[New process 26801]
#0  0x00007f74e4000850 in ?? ()
(gdb) bt
#0  0x00007f74e4000850 in ?? ()
#1  0x000000000060abf1 in Client::GetReverseFactionCon (this=0x7f74e443f260,
    iOther=0x7f74e43f42b0) at faction.cpp:180
#2  0x0000000000718d5e in Mob::CheckWillAggro (this=0x7f74e41a2c30,
    mob=0x7f74e443f260) at aggro.cpp:312
#3  0x0000000000718fca in EntityList::CheckClientAggro (this=0xbdcfa0,
    around=0x7f74e443f260) at aggro.cpp:45
#4  0x00000000005c1156 in Client::Process (this=0x7f74e443f260)
    at client_process.cpp:672
#5  0x0000000000585ff0 in EntityList::MobProcess (this=0xbdcfa0)
    at entity.cpp:487
#6  0x00000000005d1c6c in main (argc=1, argv=0x7ffff75141e8) at net.cpp:494
(gdb) frame 6
#6  0x00000000005d1c6c in main (argc=1, argv=0x7ffff75141e8) at net.cpp:494
494                                             entity_list.MobProcess();
(gdb) print zone->short_name
$1 = 0x1aff910 "erudsxing"
(gdb) frame 1
#1  0x000000000060abf1 in Client::GetReverseFactionCon (this=0x7f74e443f260,
    iOther=0x7f74e43f42b0) at faction.cpp:180
180             if (iOther->GetPrimaryFaction() < 0)
(gdb) print name
$2 = "Xion\000me", '\0' <repeats 56 times>
(gdb) print iOther->name
$3 = "Shao\000me", '\0' <repeats 56 times>
(gdb)

[mmaker]

Originally Posted by OscarGrouch05

What's up with the nulls in the characters' names?

That question is a couple of months old now, but in case it helps with future debugging I presume they're defined as char[64] instead of char*, so gdb prints out the full 64 character array. Which could contain any old junk after the first null.