help

Posted by Gorock on Sat 29 Oct 2005 05:27 PM — 7 posts, 29,760 views.

#0
ok i ran gdb and here is where i got too

#0 0x400b3d61 in ?? ()
#1 0x400b3fa4 in ?? ()
#2 0x0806142b in do_whisper (ch=0x80c8f08, argument=0x80c54e8 "\001")
at act_comm.c:1078
#3 0x08061394 in do_whisper (ch=0x0,
argument=0x1f2f <Address 0x1f2f out of bounds>) at act_comm.c:1061
#4 0x08063440 in do_repeat (ch=0x80c54e8,
argument=0xffffffff <Address 0xffffffff out of bounds>) at act_comm.c:1630
#5 0x080635ab in do_emote (ch=0x80c9f28,
argument=0xffffffff <Address 0xffffffff out of bounds>) at act_comm.c:1683
#6 0x0804c964 in imc_write_packet (p=0x1) at imc.c:1539
#7 0x0804ad46 in imc_delete_info () at imc.c:801
#8 0x4009fbb4 in ?? ()


now i went into act_comm.c and here is line 1078

if( !IS_SET( ch->in_room->room_flags, ROOM_SILENCE ) )

but i have no idea what gdb is talking about any help on learning to read what gdb is saying
USA #1
Are you sure the MUD is setup correctly for gdb? The first two stacks are missing. They shouldn't be.
#2
im using smaug fuss it should be able to be used if not im not sure how to know i read the gdb manual but it did not seem to fit my mud
USA #3
Why not? It should "fit" fine.
#4
what i mean is that some of the things were were talking about i did not see
USA #5
That stack is blown, the code path it claims to have gone through cannot happen. Delete the core, run the mud again, and debug it when it crashes the next time. Don't make any code changes in between so you can isolate this properly.
Australia Forum Administrator #6

Debugging - if you have problems with program crashes (access violation, segmentation fault etc.) try looking at the postings about debugging with gdb for some hints on using the GNU debugger.