Re: Regarding memory leaks

2006-08-28 Thread Alan DeKok 
"Ravi S M" <[EMAIL PROTECTED]> wrote:
> I am integrating my rlm_otp module with freeradius code . if I run
> radiusd server with the purify it is giving leaks

   The information you provided doesn't help to determine where
the bugs are located.  There's one mention of a C file, and tons of
other "issues" that aren't related to any C file.

  Can you convince purify to give useful information, and then post
that here?

  Alan DeKok.
--
  http://deployingradius.com   - The web site of the book
  http://deployingradius.com/blog/ - The blog
- 
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html

Regarding memory leaks

2006-08-25 Thread Ravi S M 








Hi 

 

I am integrating my rlm_otp module with freeradius code . if
I run radiusd server with the purify it is giving leaks

 

As MLK :95 bytes

 

Finished 
radiusd 
( 278 errors, 95 leaked bytes)

  Purify instrumented
/home/ravis/kshitij/freeradius-1.1.2/src/main/.libs/radiusd (pid 8830 at Fri
Aug 25 12:54:30 2006)

  Command-line: radiusd 

  UMR: Uninitialized memory
read (18 times)

  UMR: Uninitialized memory
read (19 times)

  UMR: Uninitialized memory
read (6 times)

  UMR: Uninitialized memory
read (79 times)

  UMR: Uninitialized memory
read (96 times)

  UMR: Uninitialized memory
read (3 times)

  UMR: Uninitialized memory
read (2 times)

  UMR: Uninitialized memory
read

  ABR: Array bounds read (7
times)

  ABR: Array bounds read (7
times)

  ABR: Array bounds read (7
times)

  ABR: Array bounds read (3
times)

  ABR: Array bounds read (3
times)

  ABR: Array bounds read (3
times)

  UMR: Uninitialized memory
read (8 times)

  UMR: Uninitialized memory
read (3 times)

  UMR: Uninitialized memory
read (3 times)

  PAR: Bad function parameter
(7 times)

  ABR: Array bounds read

  ABR: Array bounds read

  ABR: Array bounds read

  Current file descriptors in
use: 7

  Memory leaked: 95 bytes
(0.0142%); potentially leaked: 0 bytes (0%)

 MLK: 95
bytes leaked in 7 blocks

 This memory
was allocated from:

  
malloc     [rtlib.o]

  
lt_emalloc [ltdl.c:863]

 
lt_emalloc (size)

  
size_t size;

 
{

  
=>   lt_ptr mem = lt_dlmalloc (size);

   
if (size && !mem)

  
   LT_DLMUTEX_SETERROR (LT_DLSTRERROR (NO_MEMORY));

   
return mem;

  
canonicalize_path [ltdl.c:2044]

   
assert (path && *path);

   
assert (pcanonical);

 


  
=>   canonical = LT_EMALLOC (char, 1+ LT_STRLEN (path));

 


   
if (!canonical) 

 
return 1;

  
try_dlopen [ltdl.c:2562]

  
lt_dlopenext   [ltdl.c:2959]

  
linkto_module  [modules.c:207]

 Block of 19
bytes at 0x32ed90

 Block of 15
bytes at 0x231728

 Block of 14
bytes at 0x22c9e0

 Block of 12
bytes (3 times); last block at 0x2122b8

 Block of 11
bytes at 0x32e480

 Purify Heap
Analysis (combining suppressed and unsuppressed blocks)

  Thread Summary : 1 thread(s)
in existence

  Program exited with status
code 0.

 

 

So please provide some usefull inputs to solve this problem

 

Thanks & regards

 

Ravi









Tech Mahindra, formerly Mahindra-British Telecom.
 
Disclaimer:

This message and the information contained herein is proprietary and confidential and subject to the Tech Mahindra policy statement, you may review at http://www.techmahindra.com/Disclaimer.html externally and http://tim.techmahindra.com/Disclaimer.html internally within Tech Mahindra.


- 
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html

Re: Regarding memory leaks

2006-08-18 Thread Alan DeKok 
"Ravi S M" <[EMAIL PROTECTED]> wrote:
> So after all these if I run again
...
> ./radiusd  ->  it is giving memory leaks

  Quite frankly, I don't believe that.  You're saying that the server
somehow "remembers" what it did from one invocation to another, and
leaks memory the second time, but not the first?

  And again, you didn't provide information about the leaks.

  Alan DeKok.
--
  http://deployingradius.com   - The web site of the book
  http://deployingradius.com/blog/ - The blog
- 
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html

Regarding memory leaks

2006-08-18 Thread Ravi S M 








Hi 

 

I am using free radius code in that I have changed the log
file for using my own log file.

 

So if I run 

 

./radiusd –X  it works fine i.e. -> without any
memory leaks 

 

And also if I run  

 

./radiusd   ->  it is not generating memory leaks.

 

But if I run 

 

./radiusd –l “path/log”  ->  it is giving
memory leaks 

 

So after all these if I run again

 

./radiusd  ->  it is giving memory leaks 

 

All the above I have compiled with purifier .

 

So what might be the problem, please give some useful
comments on this.

 

Thanks & Regards

 

Ravi 

 

 









Tech Mahindra, formerly Mahindra-British Telecom.
 
Disclaimer:

This message and the information contained herein is proprietary and confidential and subject to the Tech Mahindra policy statement, you may review at http://www.techmahindra.com/Disclaimer.html externally and http://tim.techmahindra.com/Disclaimer.html internally within Tech Mahindra.


- 
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html