I have just mentioned only the major memory leaks.
==11471== LEAK SUMMARY:
==11471== definitely lost: 481728 bytes in 16476 blocks.
==11471== indirectly lost: 30728880 bytes in 352127 blocks.
==11471== possibly lost: 21299 bytes in 148 blocks.
==11471== still reachable: 15977295 bytes in 252536 blocks.
==11471== suppressed: 0 bytes in 0 blocks.==11471== 25872460 (2184 direct, 25870276 indirect) bytes in 42 blocks
are definitely lost in loss record 467 of 547
==11471== at 0x1B903407: operator new(unsigned)
(vg_replace_malloc.c:132)
==11471== by 0x807792D:
DFA_Machine::StateSetToDFA_State(NFA_StatePList*, DFA_State*&,
EquivClass const*) (DFA.cc:629)
...
==11471== 1874712 (117120 direct, 1757592 indirect) bytes in 3660 blocks
are definitely lost in loss record 217 of 547
==11471== at 0x1B903407: operator new(unsigned)
(vg_replace_malloc.c:132)
==11471== by 0x80E209E: make_alternate(NFA_Machine*, NFA_Machine*)
(NFA.cc:329)
Hmmm, looks like a leak in regular-expression matching. Could you send
me (offline) the scripts you're using and perhaps an example of the sort
of traffic your analyzing with them? I'd like to see if I can get Purify
to reproduce the problem.
Vern