[AGENT++] Bug in NotificationOriginator->add_v3_trap_destination()?

[Joshua Pressnell]

Jochen,

Thanks for the additional tips.. through my testing yesterday I have one
more tidbit that might aide in finding the source.  I removed *all* code
in the agent.  I then allocate one Mib object.  Without putting anything
in it, I then immediately delete it.  This still causes a crash.  

I will attempt further traces to pinpoint the issue on Monday.

-Josh

-----Original Message-----
From: Jochen Katz <katz at agentpp.com>
To: agentpp at agentpp.org
Cc: Frank Fock <fock at agentpp.com>
Date: Sat, 04 Feb 2006 00:09:35 +0100
Subject: Re: [AGENT++] Bug	in
NotificationOriginator->add_v3_trap_destination()?

> Hi Josh,
> 
> > I now have the agent itself working perfectly... but if I attempt to
> > shutdown the agent, I receive an access violation during the "delete
> > mib" call.  I tracked down the error to the clearing of contexts.  If
> I
> > try to call mib->remove_context() first, I crash there.  The crash
> > *seems* to be occuring during the destructor of an OctetStr within
> the
> > default context, but that could be a bad trace...
> 
> just go up in the stack frames to see which other mib classes are
> involved. Then you have the Mibgroup/MibTable/MibLeaf class that causes
> the crash.
> 
> > Is there anything special I need to do to cleanup the generated
> system
> > and variables before deleting them?
> 
> The only thing you should do before deleting the mib is to make sure
> that there are no active threads that process requests:
> 
> while (!mib->get_thread_pool()->is_idle())
>   sleep(...)
> 
> Regards,
>   Jochen
> _______________________________________________
> AGENTPP mailing list
> AGENTPP at agentpp.org
> http://lists.agentpp.org/mailman/listinfo/agentpp


--
-- Official RTI e-mail  ---
--