<div dir="ltr">Thanks. I noticed that the reset function is not called when I exit hostapd. So I can;t seem to free all the memory. </div><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Jul 29, 2014 at 11:39 PM, Jouni Malinen <span dir="ltr"><<a href="mailto:j@w1.fi" target="_blank">j@w1.fi</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5">On Tue, Jul 29, 2014 at 08:39:41AM +0300, khali singh wrote:<br>
> I have now a working new EAP method that satifies my needs. But giving my<br>
> coding skills, I want to know if there are memory leaks. IS there some easy<br>
> to use tool for this. I have some experience with valgrind. But my hostapd<br>
> should never stop running. Only at the end of an eap run, successful or<br>
> unsuccessful, all the memory should be released. Is there some easy way out?<br>
<br>
</div></div>hostapd does not use per-EAP session memory allocation mechanism, so it<br>
would be difficult to do that without stopping the process. I would just<br>
run an authentication run (or few) and stop the process to check for<br>
memory leaks. If you are using the os_*alloc functions, you can use<br>
internal memory allocation validation code (CONFIG_WPA_TRACE=y) to get<br>
list of memory leaks when the process exists. valgring is also a pretty<br>
convenient way of doing this.<br>
<span class="HOEnZb"><font color="#888888"><br>
--<br>
Jouni Malinen PGP id EFC895FA<br>
_______________________________________________<br>
HostAP mailing list<br>
<a href="mailto:HostAP@lists.shmoo.com">HostAP@lists.shmoo.com</a><br>
<a href="http://lists.shmoo.com/mailman/listinfo/hostap" target="_blank">http://lists.shmoo.com/mailman/listinfo/hostap</a><br>
</font></span></blockquote></div><br></div>