Re: tcl/expect locked up

Thanks Earl and Cameron,
I was careless with my included sample and failed to clarify that the
send strings included "\r" chars, rest assured these are in there :)

As for anchoring the prompt in an "expect -re" block, I understand this
good practice, but the output for all of these register read/write
commands is extremely regular (the command line has a standard output
for every transaction) and the 100+ expect statements prededing the
error work fine in the script so I am doubtful this is the issue (and
no, there are no prompt-like chars in the formated output...)

The suggestion for a timeout implemented on every expect is a great
suggestion, I will test this out and give everyone feedback.

The thing that is so strange is that this error occurs at the same line
in the tcl/expect script everytime as if some buffer had filled up.

The script structure and its expected output are extremely regular: The
tcl/expect script was generated by a separate perl script (not my
choice) so this script has the heaviest use of uber-simple, repeating
"send/expect" transactions I have ever seen (several hundred if not
thousands).

I have 5+ years of expect automation but this is a new phenomenon for
me, however this is a new use of expect in my experience.

-Adam
Received on Thu Sep 29 14:36:35 2005