Code:
[/i]
if (!SCRIPT_CHECK(ch, MTRIG_GREET | MTRIG_GREET_ALL) ||
!AWAKE(ch) || FIGHTING(ch) || (ch == actor) ||
AFF_FLAGGED(ch, AFF_CHARM))
continue;
Code:
==9054== Invalid read of size 8
==9054== at 0x1ABA90: greet_mtrigger (dg_triggers.c:241)
==9054== by 0x129DAC: do_simple_move (act.movement.c:194)
==9054== by 0x165812: mobile_activity (mobact.c:96)
==9054== by 0x146CED: heartbeat (comm.c:897)
==9054== by 0x14A681: game_loop (comm.c:857)
==9054== by 0x14A9AA: init_game (comm.c:427)
==9054== by 0x115F31: main (comm.c:362)
==9054== Address 0x4d23680 is 32 bytes before a block of size 144 in arena "client"
==9054==
==9054== Invalid read of size 1
==9054== at 0x1ABA9C: greet_mtrigger (dg_triggers.c:241)
==9054== by 0x129DAC: do_simple_move (act.movement.c:194)
==9054== by 0x165812: mobile_activity (mobact.c:96)
==9054== by 0x146CED: heartbeat (comm.c:897)
==9054== by 0x14A681: game_loop (comm.c:857)
==9054== by 0x14A9AA: init_game (comm.c:427)
==9054== by 0x115F31: main (comm.c:362)
==9054== Address 0xd0 is not stack'd, malloc'd or (recently) free'd
==9054==
==9054==
==9054== Process terminating with default action of signal 11 (SIGSEGV)
==9054== Access not within mapped region at address 0xD0
==9054== at 0x1ABA9C: greet_mtrigger (dg_triggers.c:241)
==9054== by 0x129DAC: do_simple_move (act.movement.c:194)
==9054== by 0x165812: mobile_activity (mobact.c:96)
==9054== by 0x146CED: heartbeat (comm.c:897)
==9054== by 0x14A681: game_loop (comm.c:857)
==9054== by 0x14A9AA: init_game (comm.c:427)
==9054== by 0x115F31: main (comm.c:362)
==9054== If you believe this happened as a result of a stack
==9054== overflow in your program's main thread (unlikely but
==9054== possible), you can try to increase the size of the
==9054== main thread stack using the --main-stacksize= flag.
==9054== The main thread stack size used in this run was 8388608.
==9054==
==9054== HEAP SUMMARY:
==9054== in use at exit: 3,037,791 bytes in 30,507 blocks
==9054== total heap usage: 33,315 allocs, 2,808 frees, 4,458,974 bytes allocated
==9054==
==9054== 4 bytes in 1 blocks are definitely lost in loss record 3 of 128
==9054== at 0x483B7F3: malloc (in /usr/lib/x86_64-linux-gnu/valgrind/vgpreload_memcheck-amd64-linux.so)
==9054== by 0x493850E: strdup (strdup.c:42)
==9054== by 0x14C844: load_help (db.c:1977)
==9054== by 0x152EA8: index_boot (db.c:933)
==9054== by 0x153BE4: boot_db (db.c:530)
==9054== by 0x14A976: init_game (comm.c:415)
==9054== by 0x115F31: main (comm.c:362)
==9054==
==9054== LEAK SUMMARY:
==9054== definitely lost: 4 bytes in 1 blocks
==9054== indirectly lost: 0 bytes in 0 blocks
==9054== possibly lost: 0 bytes in 0 blocks
==9054== still reachable: 3,037,787 bytes in 30,506 blocks
==9054== suppressed: 0 bytes in 0 blocks
==9054== Reachable blocks (those to which a pointer was found) are not shown.
==9054== To see them, rerun with: --leak-check=full --show-leak-kinds=all
==9054==
==9054== For lists of detected and suppressed errors, rerun with: -s
==9054== ERROR SUMMARY: 3 errors from 3 contexts (suppressed: 0 from 0)
Segmentation fault (core dumped)