I have seen such behaviour before- since fprintf does malloc's off the
memory heap, sometimes memory overwrites in user code can break fprintf.
This is my guess regarding the problem.
Can the person/persons responsible for the tagger code please
investigate this? If you need more details, please contact me.
Thanks.
--
Regards,
D. P. Weygand
Thomas Jefferson National Accelerator Facility
Phone: (757) 269-5926
FAX: (757) 269-5800
weygand@cebaf.gov
http://www.sura.org/~weygand