Re: mib2c for oid type cause segmentation fault, e.g. etherStatsDataSource

[Emi . Yanagi]

Robert,

Yes, I was running with -Dall option when "Broken pipe" happened. Then what is the condition that -Dall will not cause "Broken pipe"?

If running without debug option, snmpwalk on etherStatsDataSource works okay now.
Thanks for the patch, it fixed the mib2c oid type segmentation fault problem.
--
Emi

Robert Story <[EMAIL PROTECTED]>








Robert Story <[EMAIL PROTECTED]> 
07/27/2005 07:20 PM

Please respond to
net-snmp-coders@lists.sourceforge.net








To
[EMAIL PROTECTED]


cc
net-snmp-coders@lists.sourceforge.net


Subject
Re: mib2c for oid type cause segmentation fault, e.g. etherStatsDataSource








On Tue, 26 Jul 2005 11:34:37 -0500 [EMAIL PROTECTED] wrote:
EYC> trace: netsnmp_unix_send(): snmpUnixDomain.c, 160:
EYC> netsnmp_unix: send 20 bytes to 0x80bbfe0 on fd 5
EYC> Broken pipe

Were you running in a debugger? A broken pipe would be if either side shut down
the connections (maybe because of a timeout)...

-- 
NOTE: messages sent directly to me, instead of the lists, will be deleted
      unless they are requests for paid consulting services.

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.