ptx bug (invalid read)

[Cristian Cadar]

   Hello, I found an older bug report generated by our tool for ptx,
which I forgot to report.  The bug is still present in the current
version of Coreutils (6.12).  I did not have time to investigate the
root cause of the bug, but I'm including a very simple test case and the
output reported by valgrind:
 
$ echo -n a>A && valgrind ptx x A
==9357== Memcheck, a memory error detector.
==9357== Copyright (C) 2002-2007, and GNU GPL'd, by Julian Seward et al.
...
==9357== Invalid read of size 1
==9357==    at 0x804B0F5: define_all_fields (ptx.c:1516)
==9357==    by 0x804BF64: generate_all_output (ptx.c:1846)
==9357==    by 0x804C9D9: main (ptx.c:2218)
==9357==  Address 0x4022391 is 0 bytes after a block of size 1 alloc'd
==9357==    at 0x40054E5: malloc (vg_replace_malloc.c:149)
==9357==    by 0x804F4C5: xmalloc (xmalloc.c:49)
==9357==    by 0x804984C: swallow_file_in_memory (ptx.c:547)
==9357==    by 0x804C994: main (ptx.c:2203)
                                       a
                                       a
...

   Best,
   Cristian