I'm trying to run AFKMud for the first time, I create a new character and when I go to enter the MUD shuts down and reboots with this error.
*** buffer overflow detected ***: ../src/afkmud terminated
======= Backtrace: =========
/lib/i386-linux-gnu/libc.so.6(__fortify_fail+0x50)[0xdd1df0]
/lib/i386-linux-gnu/libc.so.6(+0xe4cca)[0xdd0cca]
/lib/i386-linux-gnu/libc.so.6(__strcpy_chk+0x3f)[0xdd005f]
../src/afkmud(_Z8show_mapP9char_dataPc+0x2f3)[0x819ddbd]
../src/afkmud(do_look+0x2f2)[0x80a72c0]
../src/afkmud(_Z9interpretP9char_dataSs+0xfda)[0x8149c13]
../src/afkmud(_Z12char_to_gameP9char_data+0x31c)[0x816852b]
../src/afkmud(_ZN15descriptor_data5nannyERSs+0x2c1b)[0x816b6ef]
../src/afkmud(_Z13process_inputv+0x2a5)[0x8144052]
../src/afkmud(_Z9game_loopv+0x65)[0x814428c]
../src/afkmud(main+0x1fd)[0x81451e2]
/lib/i386-linux-gnu/libc

I'm using this on the newest Ubuntu Compilies just fine.

Hrm. I've never been able to replicate this using a Fedora system. Would it be possible for you to run the game under GDB so it will crash and allow you to analyze it that way? The backtrace output is helpful to isolate to the function that's causing it, but line numbers would be infinitely more helpful.

I'll need some instrucdtions on how to do that please.

You can either use the GDB tutorial linked in our menu, or follow the one Nick Gammon has on his site: http://www.gammon.com.au/forum/?id=3653

Let me know if this information is good enough to help figure this out.

Program received signal SIGABRT, Aborted.
0x0012e416 in __kernel_vsyscall ()
(gdb) bt
#0  0x0012e416 in __kernel_vsyscall ()
#1  0x002e0e71 in raise () from /lib/i386-linux-gnu/libc.so.6
#2  0x002e434e in abort () from /lib/i386-linux-gnu/libc.so.6
#3  0x00317577 in ?? () from /lib/i386-linux-gnu/libc.so.6
#4  0x0039bdf0 in __fortify_fail () from /lib/i386-linux-gnu/libc.so.6
#5  0x0039acca in __chk_fail () from /lib/i386-linux-gnu/libc.so.6
#6  0x0039a05f in __strcpy_chk () from /lib/i386-linux-gnu/libc.so.6
#7  0x0819ddbd in strcpy (ch=0x871e238, 
    text=0x836bd2c "&cA thunderous roar echoes through the sky..... and suddenly you are transported into this tiny room! An odd blue mist begins to slowly fill the room, clouding your vision and giving you a very strang"...)
    at /usr/include/bits/string3.h:105
#8  show_map (ch=0x871e238, 
    text=0x836bd2c "&cA thunderous roar echoes through the sky..... and suddenly you are transported into this tiny room! An odd blue mist begins to slowly fill the room, clouding your vision and giving you a very strang"...)
    at mapper.cpp:606
#9  0x080a72c0 in do_look (ch=0x871e238, argument=...) at act_info.cpp:1221
#10 0x08149c13 in interpret (ch=0x871e238, argument=...) at commands.cpp:814
#11 0x0816852b in char_to_game (ch=0x871e238) at descriptor.cpp:2258
#12 0x0816b6ef in descriptor_data::nanny (this=0x8713ac8, argument=...)
    at descriptor.cpp:3307
#13 0x08144052 in process_input () at comm.cpp:862
---Type <return> to continue, or q <return> to quit---
#14 0x0814428c in game_loop () at comm.cpp:935
#15 0x081451e2 in main (argc=<value optimized out>, argv=Cannot access memory at address 0x7cec
) at comm.cpp:1342

If that big long line of text is being fed to the strcpy commands in this function that would explain it. They're way too long for the buffer size. The code should have isolated the color tag at the front but obviously didn't.