Re: net-snmp dumping core in internal_register_config_handler

Hi,

Please ignore the previous mail, as I was able to figure out the problem.
The crash was happening, due to passsing of null value to init_snmp. This
used to work fine in UCD 4.2.X. Now it seems, that it is mandatory to pass
the type value to init_snmp api.

If that is so, then can you please let us know what is type value that needs
to be passed to init_snmp api to avoid the reading of configuration files
etc.


Thanks in advance for doing this favour.

Dev

On Mon, Aug 18, 2008 at 1:46 PM, Devender Reddy <[email protected]>wrote:

>  Hi,
>
> As part of IPV6 support, I was  trying to upgrade the snmp version from ucd
> 4.2 .x to net-snmp 5.2.1.  So, as part of this, I did the following
> things:
>
> 1) configure --enable-ipv6  - for enabling  ipv6
> 2) make
>
> Once this is done, I copied the libnetsnmp.a to the lib location and
> modified the header files to reflect it to the net-snmp header files,
> instead of ucd.
>
> After doing all this, when I ran my application, it generated the following
> core.
>
>  #0  0x0080a083 in strchr () from /lib/tls/libc.so.6
> #1  0x08f399f5 in internal_register_config_handler (type_param=0xbfff9ab5
> "", token=0x946070f "defDomain",
>     parser=0x8f49400 <netsnmp_register_user_domain>, releaser=0x8f49530
> <netsnmp_clear_user_domain>,
>     help=0x94606fc "application domain", when=0) at read_config.c:161
> #2  0x08f39c13 in register_config_handler (type=0x0, token=0x0, parser=0,
> releaser=0, help=0x0) at read_config.c:288
> #3  0x08f39a61 in internal_register_config_handler (type_param=0x9460719
> "snmp:", token=0x946070f "defDomain",
>     parser=0x8f49400 <netsnmp_register_user_domain>, releaser=0x8f49530
> <netsnmp_clear_user_domain>,
>     help=0x94606fc "application domain", when=0) at read_config.c:174
> #4  0x08f39c13 in register_config_handler (type=0x0, token=0x0, parser=0,
> releaser=0, help=0x0) at read_config.c:288
> #5  0x08f49d16 in netsnmp_register_service_handlers () at
> snmp_service.c:342
> #6  0x08f200a4 in init_snmp (type=0x0) at snmp_api.c:829
> From the above stack trace, it's pretty clear that frame 2 type value is
> getting 0, even though frame 3 is sending a valid type value "snmp:".
>
> Has any one seen this problem, if so, then what is the remedy for this.
>
> Thanks in advance for doing this favour.
>
> --
> Thanks & Regards
> Dev
>
>


-- 
Thanks & Regards
Dev

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/

_______________________________________________
Net-snmp-users mailing list
[email protected]
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users