Bug 457179

Description of problem:
$subject

Version-Release number of selected component (if applicable):
mcstrans-0.2.7-1.el5

How reproducible:
Any

Steps to Reproduce:
1.run valgrind
# valgrind --leak-check=full --show-reachable=yes /sbin/mcstransd

2.issue (e.g.)id command. Because id command with -Z option connect /var/run/setrans/.setrans-unix
# id -Z

3.kill mcstransd
# kill `pidof valgrind`
[root@localhost ~]# ==5494== 
==5494== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 17 from 1)
==5494== malloc/free: in use at exit: 247 bytes in 12 blocks.
==5494== malloc/free: 321 allocs, 309 frees, 76,605 bytes allocated.
==5494== For counts of detected errors, rerun with: -v
==5494== searching for pointers to 12 not-freed blocks.
==5494== checked 125,692 bytes.
==5494== 
==5494== 16 bytes in 1 blocks are still reachable in loss record 1 of 2
==5494==    at 0x48054BB: realloc (vg_replace_malloc.c:306)
==5494==    by 0x31BF: main (mcstransd.c:312)
==5494== 
==5494== 
==5494== 231 bytes in 11 blocks are definitely lost in loss record 2 of 2
==5494==    at 0x48053C0: malloc (vg_replace_malloc.c:149)
==5494==    by 0x697D9F: strdup (in /lib/libc-2.5.so)
==5494==    by 0x1B8A: translate_raw (mcstrans.c:426)
==5494==    by 0x2239: trans_context (mcstrans.c:451)
==5494==    by 0x360A: main (mcstransd.c:88)
==5494== 
==5494== LEAK SUMMARY:
==5494==    definitely lost: 231 bytes in 11 blocks.
==5494==      possibly lost: 0 bytes in 0 blocks.
==5494==    still reachable: 16 bytes in 1 blocks.
==5494==         suppressed: 0 bytes in 0 blocks.
  
Actual results:
231 bytes memory leak has occurred.

Expected results:
No memory leak

Additional info: