Cloning an active text reader appears to corrupt memory -- later crash

[GoogleCodeExporter]

Please manually word wrap your text to about 60-68 chars per line
or use the ruler below as a guide.
==a=65=character=ruler=to=wrap=your=text=with====================

Problem: Create a FileObject, configure it as a Text Reader, set 
file name to a pre-existing text file. Clone the object. The C 
and R outputs display the wrong size and there is strong evidence 
that memory is corrupted. After much more use with same circuit, 
ABox is likely crash randomly.
1) Create a label object, clone it without entering any text, 
   where did that weird text come from?)
2) Doing #1 in the debug version (inside a debugger) will report 
   a memory corruption error.

Discussion: 
*) This problem appears to require a classic bug-hunt safari. 
 Single stepping through the source as the file object is 
 cloned might be a place to start. 
*) Additionally, the ABox2Rip utility might be incorporated 
 into the debug version. When cloning, the selected objects 
 are stored into a small save file, then that file a pasted 
 into the circuit. ABoxRip could be retrofitted to check 
 the temporary file.

Original issue reported on code.google.com by andyt7...@gmail.com on 12 Jul 2011 at 1:46

[GoogleCodeExporter]

First fix involves making sure label text gets terminated.
Still a problem when cloning active csv reader:
   Appears to be double parsing.
   More troubleshooting is needed.

Original comment by andyt7...@gmail.com on 13 Jul 2011 at 7:04

• Changed state: Started