[Olsr-dev] Memory Leak in olsrd git stable, how to debug ?
Gioacchino Mazzurco
(spam-protected)
Tue Nov 2 17:07:58 CET 2010
here is the output after some minutes
2010/11/2 Henning Rogge <(spam-protected)>
> On Mon November 1 2010 22:05:45 Gioacchino Mazzurco wrote:
> > I am returned now in Pisa and found olsrd ran with valgrind eating 300MB
> of
> > memory
> > but the file callgrind.out.31140 is empty
> Callgrind is the profiler tool...
>
> try "valgrind --leak-check=full --track-origins=yes --show-reachable=yes
> olsrd
> -f <configfile> -d 0" and look at the output.
>
> Henning Rogge
>
> --
> Diplom-Informatiker Henning Rogge , Fraunhofer-Institut für
> Kommunikation, Informationsverarbeitung und Ergonomie FKIE
> Kommunikationssysteme (KOM)
> Neuenahrer Straße 20, 53343 Wachtberg, Germany
> Telefon +49 228 9435-961, Fax +49 228 9435 685
> mailto:(spam-protected) http://www.fkie.fraunhofer.de
> GPG: E1C6 0914 490B 3909 D944 F80D 4487 C67C 55EC CFE0
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.olsr.org/pipermail/olsr-dev/attachments/20101102/381a740b/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: valgrind_output
Type: application/octet-stream
Size: 28729 bytes
Desc: not available
URL: <http://lists.olsr.org/pipermail/olsr-dev/attachments/20101102/381a740b/attachment.obj>
More information about the Olsr-dev
mailing list