[AWS] Test program to showcase the AWS.SMTP.Client.Send leak

[Georg Bauhaus]

On 23.06.11 10:15, Thomas Løcke wrote:
> https://github.com/ThomasLocke/foobar
> 
>     $ git clone git://github.com/ThomasLocke/foobar.git
>     $ cd foobar
>     $ gnatmake -P foobar.gpr
>     $ valgrind -v --leak-check=full --track-origins=yes exe/foobar
> 
> It doesn't leak when the SMTP host is good. It leaks when the SMTP host is bad.
> 
> At least that is the case here. I've tested it with both GNAT GPL 2010
> and 2011. Both show the leak.

I see the same effect here, using

$ which gcc
/usr/local/bin/gcc   # recent FSF

$ gcc -v
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/local/libexec/gcc/i686-pc-linux-gnu/4.7.0/lto-wrapper
Target: i686-pc-linux-gnu
Configured with: /opt/src/configure --enable-languages=c,ada --disable-nls
Thread model: posix
gcc version 4.7.0 20110610 (experimental) (GCC)

$ uname -a
Linux thymian 2.6.26-2-686 #1 SMP Sat Jun 11 14:54:10 UTC 2011 i686 GNU/Linux

$  cat /etc/debian_version
6.0.1


I have followed valgrind's advice and get some more hints,
$ valgrind -v --show-reachable=yes \
	--leak-check=full \
	--track-origins=yes exe/foobar > foobar.report.reachable.txt 2>&1

-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: foobar.report.reachable.txt
Url: /pipermail/aws/attachments/20110624/867e5bc8/attachment.txt