one problem in free_context

[GoogleCodeExporter]

What steps will reproduce the problem?
1. add ctx = NULL after free(ctx)
2. then compile the program 
3. use $ valgrind ./mongoose

What is the expected output? What do you see instead?
valgrind ./mongoose
==3213== Memcheck, a memory error detector
==3213== Copyright (C) 2002-2009, and GNU GPL'd, by Julian Seward et al.
==3213== Using Valgrind-3.6.0.SVN-Debian and LibVEX; rerun with -h for 
copyright info
==3213== Command: ./mongoose
==3213== 
Mongoose web server v.3.1(Nov  6 2011, 14:12:26) started on port(s) 8080 with 
web root [.]
^CExiting on signal 2, waiting for all threads to finish... done.
==3213== 
==3213== HEAP SUMMARY:
==3213==     in use at exit: 272 bytes in 2 blocks
==3213==   total heap usage: 34 allocs, 32 frees, 173,966 bytes allocated
==3213== 
==3213== LEAK SUMMARY:
==3213==    definitely lost: 0 bytes in 0 blocks
==3213==    indirectly lost: 0 bytes in 0 blocks
==3213==      possibly lost: 272 bytes in 2 blocks
==3213==    still reachable: 0 bytes in 0 blocks
==3213==         suppressed: 0 bytes in 0 blocks
==3213== Rerun with --leak-check=full to see details of leaked memory
==3213== 
==3213== For counts of detected and suppressed errors, rerun with: -v
==3213== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 16 from 7)

said may be have memory leak, why?
 34 allocs, 32 frees

What version of the product are you using? On what operating system?
v3.1  ubuntu 10.04

Please provide any additional information below.

Original issue reported on code.google.com by yef....@gmail.com on 6 Nov 2011 at 6:38

[GoogleCodeExporter]

Would --leak-check=full tell where the leak is?

Original comment by valenok on 6 Nov 2011 at 8:30

[GoogleCodeExporter]

thank you for attention! It almost a random, I never see it again.

Original comment by yef....@gmail.com on 7 Nov 2011 at 3:01

[GoogleCodeExporter]

Thanks.
Please reopen if you have leak evidence.

Original comment by valenok on 7 Nov 2011 at 3:15

• Changed state: WontFix