[email protected] wrote:
> Dave Shield wrote:
> Hi Dave,
>
> yes - this seems to work for the repeated snmpwalk tests (no failures
> after 40 tests - previously got one every 5-15 tests). The original
> application will have to run for 9 hours before I can verify that is
> fixed too - but
Dave Shield wrote:
> Good catch!
> Try the following tweak to the code, and see if it fixes the problem:
>
>> 419 if (netsnmp_ds_get_boolean(NETSNMP_DS_LIBRARY_ID,
>> NETSNMP_DS_LIB_16BIT_IDS))
>> 420 retVal &= 0x7fff; /* mask to 15 bits */
>> 421 else
>> 422 retV
2009/8/12 [email protected] :
> 409 long
> 410 snmp_get_next_reqid(void)
> 411 {
> 412 long retVal;
> 413 snmp_res_lock(MT_LIBRARY_ID, MT_LIB_REQUESTID);
> 414 retVal = 1 + Reqid; /*MTCRITICAL_RESOURCE */
> 415 if (!retVal)
> 416 retVal = 2;
> 417 R
Bart Van Assche wrote:
> Can you please create a bug report with the information you posted on
> the Net-SNMP coders mailing list, and also the messages printed by
> Valgrind, including the "Address ... is ... bytes inside a block of
> size ... alloc'd" information ? See also
> https://sourcef
On Wed, Aug 12, 2009 at 11:16 AM,
[email protected] wrote:
> Bart Van Assche wrote:
> > On Thu, Aug 6, 2009 at 12:02 PM,
> >> Any opinions of whether this error could be causing my glibc double free
> >> errors, or whether it is a red-herring?
> >
> > It is unlikely that the above message p
Bart Van Assche wrote:
> On Thu, Aug 6, 2009 at 12:02 PM,
>> Any opinions of whether this error could be causing my glibc double free
>> errors, or whether it is a red-herring?
>
> It is unlikely that the above message printed by Valgrind is related
> to the double free reported by glibc.
>
On Thu, Aug 6, 2009 at 1:50 PM, Bart Van Assche wrote:
> On Thu, Aug 6, 2009 at 12:02 PM,
>> Any opinions of whether this error could be causing my glibc double free
>> errors, or whether it is a red-herring?
>
> It is unlikely that the above message printed by Valgrind is related
> to the double f
2009/8/6 [email protected] :
> I inserted the memsets - and the valgrind error disapeared. Thanks for
> that - I will post this change on the patch tracker.
Don't bother - this fix has already been applied to the latest code
(as of early June) and should included in future releases.
Dave
Bart Van Assche wrote:
> On Thu, Aug 6, 2009 at 12:02 PM,
> [email protected] wrote:
>> The 1 remaining valgrind error (reproduced at the end in full) is
>> complaining about
>>
>> "socketcall.sendmsg(msg.msg_control) points to uninitialised byte(s)".
>
> Try to insert the statements "me
On Thu, Aug 6, 2009 at 12:02 PM,
[email protected] wrote:
> The 1 remaining valgrind error (reproduced at the end in full) is
> complaining about
>
> "socketcall.sendmsg(msg.msg_control) points to uninitialised byte(s)".
Try to insert the statements "memset(&cmsg, 0, sizeof(cmsg));
memset(&m, 0
Bart Van Assche wrote:
> On Tue, Aug 4, 2009 at 4:06 PM,
> [email protected] wrote:
>> I have an application using net-snmp 5.4.2.1 which after some time -
>> seemingly proportional to the number of snmp requests - will terminate
>> with a glibc double free error.
Bart Van Assche wrote:
> On Tue, Aug 4, 2009 at 4:06 PM,
> [email protected] wrote:
>> I have an application using net-snmp 5.4.2.1 which after some time -
>> seemingly proportional to the number of snmp requests - will terminate
>> with a glibc double free error.
On Tue, Aug 4, 2009 at 4:06 PM,
[email protected] wrote:
> I have an application using net-snmp 5.4.2.1 which after some time -
> seemingly proportional to the number of snmp requests - will terminate
> with a glibc double free error. The application is doing repetitive and
terminate
with a glibc double free error. The application is doing repetitive and
simple SNMP_MSG_GET requests. After some time - could be a number of
weeks, snmp_synch_response will return STAT_ERROR, and when
snmp_close(ss) is called - the double free is detected after
snmp_sess_close calls
--- jigar contractor <[EMAIL PROTECTED]> wrote:
> From: jigar contractor <[EMAIL PROTECTED]>
> Subject: glibc double free error
> To: [email protected]
> Date: Mon, 22 Aug 2005 07:33:20 -0700 (PDT)
>
> Hi,
>
> I made and
Hi,
I made and application in which sub agent is interacting with master agent. Now if I shut down subagent before master agent after some gets and sets my I am seeing error "glibc double free corruption" I don't know why this is happening ? If any of you have idea about this problem t
16 matches
Mail list logo
