Hi,
I managed to do a secure DTLS comm between my laptop (snmpget) and my embedded
device net-snmp agent.
But I noticed there's somewhere a memory leak on the Agent (embedded device)
side : I see some 12KB amount of memory taken by the agent each time it
successfully handles such request
Hi,
It seems, that there is a memory leak when reconfiguration by SIGHUP signal.
To reproduce and debug the issue I propose the following patch:
diff -rBbNuw -X ../Exclude net-snmp-5.8.org/agent/agent_read_config.c
net-snmp-5.8/agent/agent_read_config.c
--- net-snmp-5.8.org/agent
On 10/10/18 10:53 AM, Roedersheimer, Drew A. wrote:
I searched for usage of EVP_MD_CTX_free()/EVP_MD_CTX_new() and found a
similar memory leak in the generate_Ku() function within
snmplib/keytools.c.
Also this patch has been applied on the master and v5.8 branches.
Thanks for the patch
I searched for usage of EVP_MD_CTX_free()/EVP_MD_CTX_new() and found a similar
memory leak in the generate_Ku() function within snmplib/keytools.c. I had to
craft up a client app to force this error path, but Valgrind did confirm it:
==4091== 17,328 bytes in 361 blocks are definitely lost in
On 10/9/18 4:28 PM, Roedersheimer, Drew A. wrote:
After applying the patch, Valgrind shows no memory leaks.
Thanks for the patch! A slightly modified patch has been applied on the
master and v5.8 branches.
Comments or questions are welcome. My company is planning to supply
this patch to Re
I found a memory leak in the sc_hash()/sc_hash_type() function within
snmplib/scapi.c. The leak was identified by running Valgrind on a SNMP client
application which queries v3 servers using SHA/AES.
Here's an example of the Valgrind memory leak trace (using net-snmp-5.7.2-28
from
addr_in2+150
>> netsnmp_sockaddr_in2+134
>> netsnmp_tcp_create_tstring+24
>> netsnmp_tdomain_transport_full+508
>> netsnmp_transport_open_client+18
>> subagent_open_master_session+125
>> agentx_reopen_session+82
>> run_alarms+ce
>> SnmpTrapdMain+c28
>>
>
addr_in2+150
> netsnmp_sockaddr_in2+134
> netsnmp_tcp_create_tstring+24
> netsnmp_tdomain_transport_full+508
> netsnmp_transport_open_client+18
> subagent_open_master_session+125
> agentx_reopen_session+82
> run_alarms+ce
> SnmpTrapdMain+c28
>
>
> Thanks,
> Jeffry copps
&g
Are you sure it is a memory leak, or is it simply the NOTIFICATION-LOG-MIB
> implementation?
>
> Does the memory usage still increase when you run with "--
> doNotRetainNotificationLogs=yes" or the equivalent in snmptrapd.conf?
>
> Bill
>
>
> On Tue, Jul 11
Are you sure it is a memory leak, or is it simply the NOTIFICATION-LOG-MIB
implementation?
Does the memory usage still increase when you run with
"--doNotRetainNotificationLogs=yes" or the equivalent in snmptrapd.conf?
Bill
On Tue, Jul 11, 2017 at 3:12 AM, Jeffry Copps
wrote:
>
iginal Message -
> | From: "Jeffry Copps"
> | To: [email protected]
> | Sent: Tuesday, July 11, 2017 9:12:13 AM
> | Subject: Snmptrapd memory leak at log_notification
> |
> | Hi NET-SNMP,
> |
> | I have recently starting working on SNMP Trapd d
Core Services Team
Red Hat Czech, s.r.o.
- Original Message -
| From: "Jeffry Copps"
| To: [email protected]
| Sent: Tuesday, July 11, 2017 9:12:13 AM
| Subject: Snmptrapd memory leak at log_notification
|
| Hi NET-SNMP,
|
| I have recently starting worki
Hi NET-SNMP,
I have recently starting working on SNMP Trapd daemon.
And I was running a memory leak analysis on the application and came to
know that there is a leak
in the below call stack.
Could someone help me here? Or have I understood it wrong?
LeakTrack+20b07
msvcr120!malloc+5b
memdup+53
On Wed, 9 Nov 2016 16:10:33 +0530 Soubhagya wrote:
SP> Yes, we have used mib2c compiler to generate the code and which
SP> I feel it's same to MFD template.
SP>
SP> Apart from "Which method would you like to use to gather data
SP> about available rows?" option all other option we choosed is
SP> DE
Hi Robert,
Thank you for your response.
We have already implemented this table using autogeneration method. But
while doing a continuous query, I got memory leak in inetCidrRouteTable and
that's the reason I am going through all over again, specially
*_container_load() and add_ipv6_route_en
[Replying only to coders list]
On Mon, 7 Nov 2016 19:25:49 +0530 Soubhagya wrote:
SP> I have some queries with respect to memory leak in inetCidrRouteTable while
SP> continuous query to inetCidrRouteTable .
SP> [...]
SP> As part of my project, we have added a support for ipv6 route
Hi All,
I have some queries with respect to memory leak in inetCidrRouteTable while
continuous query to inetCidrRouteTable .
Valgrind report
===
7480 ==16547== 7,569,856 bytes in 3,416 blocks are definitely lost in loss
record 5,344 of 5,344
7481 ==16547==at 0x4C266B0: calloc
Hi Team,
I am facing one memory leak issue while doing a continuous query for more
than 12 hours within a interval of 5 seconds.
Used Net-snmp version : 5.7.3
This is the valgrind report.
==20640== 32 bytes in 1 blocks are definitely lost in loss record 2,210 of
5,253
==20640==at 0x4C266B0
Hi folks,
I have a peculiar memory leak from a sub-agent created with mib2c's "iterate"
configuration. Each time it processes a request, it grabs 64Kb which never
gets released. The stranger part is that this only happens on a production
system but NOT on my dev environmen
I've observed the leak with GET and v3 AuthNoPriv. I believe
that GET-NEXT and GET-BULK would show the problem also.
I am running an agent session that receives these requests.
-SEan
On Jul 8, 2014, at 11:10 AM, Bill Fenner wrote:
On Tue, Jun 24, 2014 at 3:47 AM, Sean Burke
wrote:
Hi All,
I tried running "top" while servicing SNMPv3 "get" requests. Results:
PID USER PR NI VIRT RES SHR S %CPU %MEMTIME+ COMMAND
3585 root 20 0 13168 2988 1008 S 0.0 0.1 0:00.05 snmpd
3585 root 20 0 13168 2988 1008 S 0.0 0.1 0:00.05 snmpd
3585 root 20 0 1
On Tue, Jun 24, 2014 at 3:47 AM, Sean Burke wrote:
> Hi All,
>
> I am writing to ask about this code in 5.7.2.1 snmp_api.c at line 5423.
> I am specifically concerned with the constraint pdu->command ==
> SNMP_MSG_TRAP2,
> which appears to interfere with freeing the securityStateRef for request
>
Hi All,
I am writing to ask about this code in 5.7.2.1 snmp_api.c at line 5423.
I am specifically concerned with the constraint pdu->command == SNMP_MSG_TRAP2,
which appears to interfere with freeing the securityStateRef for request command
types, e.g. GET, SET, GET-NEXT, GET-BULK.
Testing with v
);*
> *}*
>
> * SNMP_FREE(mallocbuf);*
> * return ret_val;*
> * <--- TWO LEAKS OCCUR HERE **}*
>
>
>
>
> On 03/12/2014 11:06 AM, John Zavgren wrote:
>
> Dear List:
>
> Let me apologize... the "memor
u_buf_len);**
**DEBUGINDENTADD(-8);**
**} else {**
**DEBUGINDENTADD(-4);**
**}**
**
**SNMP_FREE(mallocbuf);**
**return ret_val;**<--- TWO LEAKS OCCUR HERE
**}**
*
On 03/12/2014 11:06 AM, John Zavgren wrote:
Dear List:
Let me apologize... the "memory leak" that I reported, IS NOT a memory
leak. I should have read my email carefully before sending it.
I'm sorry for any confusion or consternation I may have created. :-(
JZ
On 03/12/2014 10:55 AM, John Zavgren wrote:
Greetings:
Memo
Greetings:
Memory is allocated in the procedure snmv3_parse(), in the file:
snmplib/snmp_api.c, at line number 3995, and leaked at line number 4004.
*/***
** * securtityParameters OCTET STRING begins after msgGlobalData **
** */**
**sec_params = data;**
**pdu->contextEngineID =
many have encountered it, but any memory leak I'd
say is a bad memory leak (besides that we in our usage encounter this
not too rarely).
The suggested way of fixing the leak has been working just fine on our
end since end of may. We applied the fix to the 5.7.2 source release,
but the patch
h seems to work fine, is to
just after the call to netsnmp_remove_and_free_agent_snmp_session add
the same routines as is available at snmp_api.c:5260 and snmp_api.c:5422
(which I can see in the git repository has been converted to the
function free_securityStateRef).
This does eliminate the memory leak on our test environment at le
Niels Baggesen writes:
> This seems to be a simple fix for the problem.
Applied.
--
Wes Hardaker
Please mail all replies to [email protected]
--
Live Security Virtual Conference
Exclusive live event
This seems to be a simple fix for the problem.
/Niels
--
Niels Baggesen - @home - Århus - Denmark - [email protected]
The purpose of computing is insight, not numbers --- R W Hamming
swrun_pstat.dif
Description: video/dv
>>>>> On Fri, 17 Feb 2012 21:46:22 +0530, said:
> If it is powered off, it triggers a memory leak; causing the size of the
> application to increase by 1mb every day.
Are you freeing the PDU when a failure occurs? If you read the
documentation on snmp_send you'll
the agent, these
information get stuck in the memory forever.
And these PDUs and the increasing "outstanding requests list" may be
reason behind the memory leak.
My questions are:
After the timeout/expire value, are these information automatically
deleted?
Or it resides in the memory
sec.
Everything worked fine if the network device is turned on.
If it is powered off, it triggers a memory leak; causing the size of the
application to increase by 1mb every day.
I am using SNMPv3 with authnoPriv security level.
I am also setting the Engine-id of the network device in
On Sat, Feb 26, 2011 at 5:48 PM, Adam Mendlik wrote:
> Here is a simple demo I put together that exemplifies the problem I'm
> seeing. If you run this code as-is, memory use will increase indefinately.
> However, if you take out the snmp_send() call and just call snmp_free_pdu(),
> memory use wil
Here is a simple demo I put together that exemplifies the problem I'm
seeing. If you run this code as-is, memory use will increase indefinately.
However, if you take out the snmp_send() call and just call snmp_free_pdu(),
memory use will remain perfectly flat. I should also mention that my
netsnmp.
Den 23-02-2011 19:07, Adam Mendlik skrev:
> My question is: is there a reason why snmp_send() is leaking memory, how
> do I fix it, or should I be using a different function in this scenario?
Are you checking the return value from snmp_send?
I seem to recall that sending traps is different, in th
Hello Adam,
If you can post a minimal example to this list that allows to reproduce the
leak I'll have a look at it.
Bart.
On Thu, Feb 24, 2011 at 6:50 PM, Adam Mendlik wrote:
> I'm using 5.5.1.pre2.
>
>
> On Thu, Feb 24, 2011 at 4:26 AM, Bart Van Assche wrote:
>
>> On Wed, Feb 23, 2011 at 7
I'm using 5.5.1.pre2.
On Thu, Feb 24, 2011 at 4:26 AM, Bart Van Assche wrote:
> On Wed, Feb 23, 2011 at 7:07 PM, Adam Mendlik wrote:
>
>> I've written a Windows service which consumes an inbound data stream and
>> sends out SNMP traps using netsnmp.lib.
>>
>> During service initialization I ca
On Wed, Feb 23, 2011 at 7:07 PM, Adam Mendlik wrote:
> I've written a Windows service which consumes an inbound data stream and
> sends out SNMP traps using netsnmp.lib.
>
> During service initialization I call:
> snmp_sess_init(&session);
> session.version = SNMP_VERSION_1;
> init_snmp("snmpapp"
I've written a Windows service which consumes an inbound data stream and
sends out SNMP traps using netsnmp.lib.
During service initialization I call:
snmp_sess_init(&session);
session.version = SNMP_VERSION_1;
init_snmp("snmpapp");
... and set session.peername, session.community, and session.comm
Thanks Dave,
I tried with 5.5, problem seems to be fixed now.
On Fri, Jul 23, 2010 at 11:46 AM, Dave Shield wrote:
> On 22 July 2010 17:32, Abhimanyu Chowdhary wrote:
> > When I do snmpwalk over mib-2, agent crashes after like 15 hours because
> of
> > memory leak I have ne
On 22 July 2010 17:32, Abhimanyu Chowdhary wrote:
> When I do snmpwalk over mib-2, agent crashes after like 15 hours because of
> memory leak I have netsnmp 5.3.1 and OS is linux(fedora).
Can you try with one of the more recent releases?
(5.3.3, 5.4.3, 5.5 or the 5.6 pre-release)
Hi ,
Valgrind report w.r.t this leak will help people to analyse the exact cause.
Regards,
Manjit
Abhimanyu Chowdhary wrote:
> Hi,
>
> When I do snmpwalk over mib-2, agent crashes after like 15 hours
> because of memory leak.
> Now, what I have seen is the memory only leaks w
Hi,
When I do snmpwalk over mib-2, agent crashes after like 15 hours because of
memory leak.
Now, what I have seen is the memory only leaks when it is going through
ipCidrRoteTable,
and it always goes down in multiple of 28K. I saw their were some issues
with this[BUG 1596638],
I patched that
On Fri, 19 Mar 2010 06:28:59 -0700 (PDT) nathan wrote:
N> I am running netsnmp on an embedded platform, and noticed that memory is
filling up very quicklyusing the same agentx sw in my laptop with memory
anlyzing tool, i found out this
5.1.2 is no longer supported. Please try and reprod
Hi,
I am running netsnmp on an embedded platform, and noticed that memory is
filling up very quicklyusing the same agentx sw in my laptop with memory
anlyzing tool, i found out this
==4815== 2,352 bytes in 4 blocks are definitely lost in loss record 75 of 75
==4815==at 0x4006AEE: ma
Le Vendredi, 12 Mars 2010 17:38:37 -0800,
Wes Hardaker a écrit :
> You're right it's not. Generally there are a number of places in the
> code (many many actually) where single-instance calls to memory
> allocation are taken and never cleaned up like they should be at
> shut-down time because we
>>>>> On Sat, 6 Mar 2010 15:18:32 -0500, "Szudy Brett-CBS035"
>>>>> said:
SB> I have version 5.5 of netsnmp. I am looking at snmp_agent.c, function
SB> init_master_agent and see a memory leak here. strdup mallocs and
SB> duplicates the string
Hi all
I have version 5.5 of netsnmp. I am looking at snmp_agent.c, function
init_master_agent and see a memory leak here. strdup mallocs and
duplicates the string into buf, but then buf is never released. It is a
local which is also never stored or returned, so it is lost forever and
not
>>>>> On Tue, 22 Dec 2009 17:53:22 -0800, Stephen Hemminger
>>>>> said:
SH> Minor memory leak, the mcpu_stats array is malloc'd but never freed.
Thanks! In the future, if you upload patches to our patch tracker we
can't miss and forget them:
htt
Minor memory leak, the mcpu_stats array is malloc'd but never freed.
--- a/agent/mibgroup/hardware/cpu/cpu_sysctl.c 2009-12-22 17:25:47.923759085
-0800
+++ b/agent/mibgroup/hardware/cpu/cpu_sysctl.c 2009-12-22 17:26:37.373759058
-0800
@@ -196,6 +196,7 @@ int netsnmp_cpu_arch
intf()
> > statement in the netsnmp_udp_fmtaddr() method (plus one more)
> >
> > See: http://pastebin.ca/1701854.
> >
> > I reckon that this was fixed later (5.5. does not have it).
>
> It was.
>
> Revision 16654 accepted the patch.
> Revision 16716 fixe
//pastebin.ca/1701854.
>
> I reckon that this was fixed later (5.5. does not have it).
It was.
Revision 16654 accepted the patch.
Revision 16716 fixed the memory leak.
I think this should be sent to the Debian Net-SNMP maintainers.
/MF
> The default patch excerpt:
>
> +
} else {
> +sprintf(tmp, "UDP: [%s]->[%s]:%hu",
> +strdup(inet_ntoa(addr_pair->local_addr)),
> +strdup(inet_ntoa(to->sin_addr)), ntohs(to->sin_port));
>
> Patch URL:
>
> http://sourceforge.net/tracker/?func=det
All,
Just to let you know that 5.4.1 as shipped by Debian applies a patch
# 1775124 that contains two strdup() inside a sprintf() statement in
the netsnmp_udp_fmtaddr() method (plus one more)
See: http://pastebin.ca/1701854.
I reckon that this was fixed later (5.5. does not have it).
Th
On Wed, 11 Mar 2009 10:41:48 + (GMT) R. wrote:
RD> I normally develop with memory leak detection turned on, so that I quickly
find out about any new leaks I might have just introduced in the code. This
strategy does not work for Net-SNMP, and it looks like it's by design,
It'
On Wed, Mar 11, 2009 at 11:41 AM, R. Diez wrote:
> I find the the suggested leak-debugging procedure cumbersome and error-prone.
> It would be
> nice if all malloc'ed memory were free'd on shutdown. I guess that would be
> inside
> snmp_shutdown(), or maybe I'm just missing some clean-up call so
Hi all:
I'm debugging my own AgentX subagent on Windows XP under Visual Studio 2005,
and, I always get a number of memory leaks reported on shutdown.
I normally develop with memory leak detection turned on, so that I quickly find
out about any new leaks I might have just introduced i
the guys who faced the same issue .. help me out to resolve the same..
Thanks
Amit
From: Amit Kumar
To: [email protected]
Sent: Wednesday, 4 March, 2009 15:54:18
Subject: memory leak on traps
Hi All ,
I am getting some m/m
Hi All ,
I am getting some m/m leak in send_v2trap .. i added one patch to avoid
this
--- net-snmp-5.4/agent/agent_trap.c 2006-09-19 20:15:26.0 +0530
+++ net-snmp-5.4_new/agent/agent_trap.c 2009-03-04 15:03:14.0 +0530
@@ -897,6 +897,7 @@ send_trap_to_sess(netsnmp_sess
@lists.sourceforge.net
Subject: Re: snmpd memory leak on overnight stress test ..
2009/2/26 Amit Kumar :
> I upgraded the net-snmp version to 5.4.2.1
> (is this the latest one?)
Yes.
> i am getting the leak only while doing walk on private mib
> (which is dynamically loaded )
> i think th
2009/2/26 Amit Kumar :
> I upgraded the net-snmp version to 5.4.2.1
> (is this the latest one?)
Yes.
> i am getting the leak only while doing walk on private mib
> (which is dynamically loaded )
> i think the problem is in net-snmp dlmod only ..
Or else it's in your private module.
So th
From: Magnus Fromreide
To: Amit Kumar
Cc: [email protected]
Sent: Thursday, 26 February, 2009 13:03:32
Subject: Re: snmpd memory leak on overnight stress test ..
On Wed, 2009-02-25 at 22:44 -0800, Amit Kumar wrote:
> please find the valgring tra
On Wed, 2009-02-25 at 22:44 -0800, Amit Kumar wrote:
> please find the valgring traces :
> ... lots of valgrind output...
> Hi All,
>
> I am using net-snmp 5.4 version . while doing overnight stress
> test i got a memory leak of 2 MB ..
> i am not able to f
Hi All,
I am using net-snmp 5.4 version . while doing overnight stress test i
got a memory leak of 2 MB ..
i am not able to figure out the problem .. please help me out ...
Thanks in Advance..
Amit Kumar
ple ? val_tuple : Py_BuildValue(""));
}
Regards,
Gabriele Messineo
-- Forwarded Message --
Subject: python snmpwalk memory leak
Date: Friday 24 October 2008
From: Gabriele Messineo <[EMAIL PROTECTED]>
To: [email protected]
Hi,
I woul
Hi,
I would like to re-open netsnmp Bug "[ 1868278 ] A bug in python useing
netsnmp.snmpwalk".
That's because cited patch (
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=497656 ) was addressing a
seg fault.
I did some tests in order to find the memory leak, I hope it ca
Hi, Zhouhuai,
I also saw the same coredump but it seemed to related to delegated requessts
on timeout in my case.
thanks,
Daniel
Zhouhuai Shen wrote:
> Hi,
>
> I had a coredump when I run net-snmp 5.3.1. It seems the leakage was
> observed when traps are sent.
> Doesanyoneknow about this issue
Hi,
I had a coredump when I run net-snmp 5.3.1. It seems the leakage was observed
when traps are sent.
Doesanyoneknow about this issue and any possible patch has been done tofix
this?It seems the problem also happens in net-snmp 5.4.1.
My coredump is as the following:
===
> On Thu, 05 Jun 2008 02:41:25 +0200, Thomas Anders <[EMAIL PROTECTED]>
> said:
TA> BTW, you've been heavily arguing against the #ifdef hack in the first
TA> place back then, but don't let it stop you from voting for its
TA> persistence now that the alternative isn't a fancy segfault, but
김성환 wrote:
>
> I am using the following function modified from the main function of
> 'snmpget' program.
>
Bear in mind that this code is a "use once" program.
It doesn't necessarily try to tidy up cleanly, since all
memory will be released automatically when the program exits.
> When I call the
Hello,
I am using the following function modified from the main function of 'snmpget' program.
The SNMP library version is 5.4.1.
But, it has a memory leak problem.
When I call the functions infinitely,
the memory size of the program grows.
How can I solve the problem?
Please, l
Hello,
I am using the following function modified from the main function of 'snmpget'
program.
The SNMP library version is 5.4.1.
But, it has a memory leak problem.
When I call the functions infinitely,
the memory size of the program grows.
How can I solve the problem?
P
Wes Hardaker wrote:
> I think without looking further into the issue, I'd say -1. If it's
> known to cause segfaults on x86_64 (as the comment applies) then it
> would be better to change the ifdef to a point where we know it's safe
> now, or go back to the original perl version that the problem a
>>>>> On Sun, 01 Jun 2008 08:51:54 +0200, Thomas Anders <[EMAIL PROTECTED]>
>>>>> said:
>> Log Message:
>> ---
>> NEWS: snmptrapd: BUG: 1955227: Memory leak for embedded Perl on x86_64
>>
>> Modified Paths:
>
[EMAIL PROTECTED] wrote:
> Revision: 16983
> http://net-snmp.svn.sourceforge.net/net-snmp/?rev=16983&view=rev
> Author: tanders
> Date: 2008-05-31 23:45:23 -0700 (Sat, 31 May 2008)
>
> Log Message:
> ---
> NEWS: snmptrapd: BUG: 1955227: Memo
Am Freitag 08 Februar 2008 17:06:02 schrieb Thomas Anders:
> Henning Rogge wrote:
> > during writing a netsnmp subagent I noticed my code had a memory leak. I
> > tracked it down to a memory leak in netsnmp.
> >
> > I attached a programm which produce the memory leak.
Henning Rogge wrote:
> during writing a netsnmp subagent I noticed my code had a memory leak. I
> tracked it down to a memory leak in netsnmp.
>
> I attached a programm which produce the memory leak.
Could you please file a bug on http://www.net-snmp.org/bugs so it won't get
Hello,
during writing a netsnmp subagent I noticed my code had a memory leak. I
tracked it down to a memory leak in netsnmp.
My code has to create and release entries in the SNMP tree and it seems that
function netsnmp_unregister_handler() does not free all resources allocated
during handler
Hello all
I've encounter with memory leak and unclose sockets in the snmp agent
-Net-SNMP version 5.3.1:
scenarios:
* for each HUP signal sent to the agent ( for configuration
update) while in the snmpd.conf include trap directive (
v1 or v2 ). for example "
hi,
the tool valgrind report there is a memory leak in function
"netsnmp_transport *netsnmp_udp_transport(struct sockaddr_in *addr, int
local)" in file "snmplib/snmpUDPDomain.c" : *addr_pair is malloced but not
freed.
The net-snmp version is 5.2.4.
I looked into
On 20/07/07, 吴亚东 <[EMAIL PROTECTED]> wrote:
>From http://net-snmp.sourceforge.net/docs/CHANGES.html, there are two:
- [PATCH 1592706]: Fix memory leak when cloning varbinds.
- [PATCH 1616912]: fix memory leak in snmp_udp_transport
But I can not find patch 1592706.
http://source
I use net-snmp 5.4 to send out enterprise-specific traps.
The trap-sending code is like agent/mibgroup/examples/notification.c
When sending trap very fast, we can see that snmpd consumes more and
more memory(up to 500M).
Is there any memory leak problem in net-snmp 5.4?
>From http://
is 5.3.1, and
> > > > Valgrind is 3.2.3. Is this kind of behavior normal from libsnmp, or is
> > > > the test program's code broken in some way?
> > >
> > > Would you mind building net-snmp 5.4.1.pre3 from source, compile the
> > > test p
>
> RS> Instead, make the release call in _mfd__post_request (in
> RS> _interface.c) unconditional.
>
OK, I've done that and it still fixes the memory leak :)
However I still have problems when inserting a new Row - see below for
the Debug (error on subcontainer '
normal from libsnmp, or is
> > > the test program's code broken in some way?
> >
> > Would you mind building net-snmp 5.4.1.pre3 from source, compile the
> > test program against it and re-run your test?
>
> Using trunk, the memory leak is due to init_snmp_enums where
On Mon, 2 Jul 2007 17:37:27 +0100 Graeme wrote:
GW> Ok, as per my previous email, I've been looking at a table which uses
GW> row-creation, and this is causing a couple of problems - although this
GW> could be related to my implementation because I'm a little unsure about
GW> a couple of things. M
007 11:13
> To: Robert Story
> Cc: [email protected]
> Subject: RE: Memory leak in agent code using mfd
>
> > RS> Ugh. The iterator style mfd code is the least tested aspect of
> > RS> this code.
>
> Oh well, I guess someone has to be the g
RS> I think that will work, but it may cause other side effects
> RS> (especially if your table supports row creation). Give it a
> RS> whirl and let me know how it goes..
Yes, I've tried this and it seems to be working much better now (no
memory leak).
My current table I've
On Thu, 28 Jun 2007 16:46:09 +0100 Graeme wrote:
GW> ==12187==by 0x8049EF0: _loop_get_first
GW> (_data_access.c:213)
GW> ==12187==by 0x804C222: __loop_get_first_wrapper
GW> (_interface.c:753)
Ugh. The iterator style mfd code is the least tested aspect of this code.
I've just run through i
Hi,
I'm having some problems with a memory leak in my agent code - the
template for which generated using the mfd config. I would appreciate
any help to solve this problem since its now becoming a serious issue
for me.
I have run the code through valgrind and observe the following dur
On mån, 2007-06-18 at 15:32 +0200, Makavy, Erez (Erez) wrote:
> Hi,
>
> Is there any reason why this function does not close the associated
> session?
No, and thus revision 15778 corrected this.
This will be available in the next net-snmp release.
Thanks for the bug report.
/MF
Hi,
Is there any reason why this function does not close the associated
session?
<-CODE-SEGMENT- [ from snmpTargetAddrEntry.c ]
void
snmpTargetAddrTable_dispose(struct targetAddrTable_struct *reaped)
{
SNMP_FREE(reaped->name);
SNMP_FREE(reaped->tAddress);
SNMP_FREE(reape
On ons, 2007-04-25 at 23:59 +0400, Aleksandr Lomanov wrote:
> Hello, Wes!
>
> I found memory leak in function netsnmp_udp_transport()
> in snmpUDPDomain.c file.
>
> Memory for variable 'addr_pair' not released,
> when netsnmp_udp_transport() finishes work.
Yes,
Hello, Wes!
I found memory leak in function netsnmp_udp_transport()
in snmpUDPDomain.c file.
Memory for variable 'addr_pair' not released,
when netsnmp_udp_transport() finishes work.
Aleksandr Lomanov
ICQ#:
On 11/04/07, Kun Niu <[EMAIL PROTECTED]> wrote:
> So I changed the snmpget source code so that it runs continuously for about
> 100,000,000 times.
> And I found that the useage of my memory grows quickly.
First question - which version of the code are you using?
We're continually plugging memory l
Dear Santhosh,
Thank you for your kind reply.
I tried your suggestion.
But it's of little help.:(
It should have already been freed within snmp_free_pdu.
Any other suggestions?
Thanks again for your reply.
-
Take Surveys. Ea
Hi,
Try freeing variable binding pdu->variables using
snmp_free_varbind().
Santhosh
==
Message: 7
Date: Thu, 12 Apr 2007 01:53:26 +0800
From: "Kun Niu" <[EMAIL PROTECTED]>
Subject: Possible snmp get memory leak?
To: [EMAIL PR
Dear coders,
I'm sorry to trouble.
I've successfully made my first snmp program on Win2000 platform with
VS2003.
It runs smoothly at the first two hours.
But it suddenly dies after that.
So I changed the snmpget source code so that it runs continuously for about
100,000,000 times.
And I found tha
1 - 100 of 160 matches
Mail list logo
