Re: *arg* debugging..

From: Fizal (amustapa@yahoo.com)
Date: 02/07/00


At 11:47 AM 7/2/2000 +0100, The Merciless Lord of Everything
<serces@mud.dk> wrote:
>And a backtrack (bt) tells:
>#0  0x0 in ?? ()
>#1  0x80b97c2 in process_events () at dg/dg_event.c:81
>#2  0x804a5d8 in heartbeat (pulse=187415) at comm.c:759
...
>#1  0x80b97c2 in process_events () at dg/dg_event.c:81
>81            e->func(e->info);
>
>print *e gives the following:
>$6 = {time_remaining = 0, func = 0, info = 0x856e208, next = 0x0}

I'm no expert in gdb either, but looking at the bt, it looks like it's
trying to call a null function. e->func is supposed to have the name of the
function to be called and e->info is supposed to be its argument. But when
you print *e, it displayed the function name as 0.

Try:
1. checking out to make sure that all entry to the event list includes the
name of the function.
2. double check to make sure that the name of the function itself is
spelled correctly.
3. make sure that the function is actually there.

G'luck!

---

Afizal Mustapa
Petaling Jaya, Selangor, Malaysia.
(amustapa@hotmail.com)

__________________________________________________
Do You Yahoo!?
Talk to your friends online with Yahoo! Messenger.
http://im.yahoo.com


     +------------------------------------------------------------+
     | Ensure that you have read the CircleMUD Mailing List FAQ:  |
     |  http://qsilver.queensu.ca/~fletchra/Circle/list-faq.html  |
     +------------------------------------------------------------+



This archive was generated by hypermail 2b30 : 04/10/01 PDT