On Wed, 2006-02-01 at 17:25 +0100, Marcus Rueckert wrote:
> after this patch i encountered a second crash in
>
> agent/mibgroup/disman/event/mteObjects.c:164
>
> i have attached the stacktrace of thise crash to this mail.
> sadly i cant run the binary in gdb for debugging it directly.
Hmmmm... that's a pity. The stack trace is only
going to be of limited use. It would be helpful to
know which bit of
row->oid_index.oids[row->oid_index.len]++;
it's objecting to, and how far through it gets.
Could you perhaps try adding a debug print statement
to that loop, that would indicate the value of the
"oid_index" OID array at the point at which it fails.
Just out of interest, why is it not possible to
run this under gdb? It would make tracking down
the problem *much* easier!
Dave
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
Net-snmp-coders mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
