> On Tue, 16 Dec 2008 12:26:22 +0530, "Venkatrangan G"
> said:
VG> My application runs on a board having just around 32 MB and getting
VG> valgrind to the box is thus impossible. Hence mtrace was the only viable
VG> option but somehow it fails to log in my case, can you please what could
Message-
From: Wes Hardaker [mailto:[email protected]]
Sent: Tuesday, December 16, 2008 4:45 AM
To: Venkatrangan G
Cc: [email protected]
Subject: Re: Reg Net-SNMP 5.4.2.1
>>>>> On Mon, 15 Dec 2008 12:58:58 +0530, "Venkatrangan G"
said:
VG
> On Mon, 15 Dec 2008 12:58:58 +0530, "Venkatrangan G"
> said:
VG> I have also tried other memory leak tools (efence, DUMA, dmalloc). Ours
VG> being an embedded application does not have enough space to operate with
VG> the debuggers, hence could not use valgrind also. Please suggest som
,
Venkatrangan
From: Venkatrangan G
Sent: Monday, December 15, 2008 12:21 PM
To: '[email protected]'
Subject: Reg Net-SNMP 5.4.2.1
Hi,
We had recently upgraded from Net-SNMP 5.1 to Net-SNMP
5.4.2.1. To
Hi,
We had recently upgraded from Net-SNMP 5.1 to Net-SNMP
5.4.2.1. To debug when we added mtrace() to the code and build snmpd for
powerpc, it fails to log to file even after setting "MALLOC_TRACE" Is
this some kind of restriction.
Thjs is my final link command
powerpc-linux-gcc -
