On Tue, 16 Nov 2004 13:29:30 +0100 P wrote: PK> 1) I wrote some mib and then generated code using mib2c with mfd.
Aha, my first victim! PK> In generated code there is no xyzTable_undo_setup function, but PK> *interface.c assumes it's defined. Same with xyzTable_undo_cleanup PK> fucntion. Right you are. Two options here: 1) set m2c_data_init to 1 in default-table-xyzTable.m2d 2) Apply the attached patch and re-generate PK> 2) snmpwalk crash. When I run snmpwalk -On myTable it works fine. PK> Where I run "snmpwalk myTable" it does not print anything, only crash PK> with sigsev. "snmpwalk ifTable" works. When I use some older snmpwalk PK> (5.0.8 or so) it works also with myTable (,,myTable'' is table defined PK> by me). If you are having problems with an application crashing, it is very helpful to have a backtrace (aka stack trace) at the point of the crash. If you can run the application with GDB and reproduce the problem, the 'backtrace' command should print this information for you. PK> I'm puzzled. I don't now if error is in my code (genrated my PK> mib2cs; same effect with one in ,,mfd'' style and one with iterator PK> style) or on some other place in net-snmp. Are these other modules also custom modules, or do you get crashes with net-snmp modules too? -- Robert Story; NET-SNMP Junkie Support: <http://www.net-snmp.org/> <irc://irc.freenode.net/#net-snmp> Archive: <http://sourceforge.net/mailarchive/forum.php?forum=net-snmp-coders> You are lost in a twisty maze of little standards, all different.
mfd-interface.pat
Description: Binary data
