Whew. This is rather a difficult mess to attack. Find out if the text editor you are using to write programs has any sort of facility for doing auto-indentation, so that it's easy to make sure that blocks of code are properly indented. If your current editor doesn't support this, look for an editor that does.

I don't actually have Expect.pm installed on my machine at the momemnt, but even if I did, I'd have no way to test your code for myself. Still, after editing a copy of it to apply proper indentation, the following points became evident:

• You need to include "use strict" and "use warnings"

• You don't seem to understand the "open" and "close" calls. The first argument to open() should either be the name you want to assign to a filehandle, in CAPS (e.g. SPCMAP, not spcmap), or else it should be a scalar variable with lexical scope:  open my $spcmap, '<', $mapfile or die ... Then, the close() call needs to be given the FILEHANDLE (i.e. first arg given to open()) -- not the name of the file that was opened.

• You don't seem to understand quantifiers and/or the "\b" operator in regular expressions; in your regex:  /\b*error1\b*/ the "*" quantifier makes no sense when applied to the "zero-width word-boundary assertion".

• Inside your while(1) loop, you read a command from STDIN, and you do one of three things depending on its content: the first thing is exit the loop if "quit " occurs anywhere in the string (no problem there); the second involves some other checks and mods -- including  chomp $cmd; and the third involves just passing $cmd to expect->send() -- without chomping it. I wonder if that might be part of the problem (I really don't know.)

Apart from that, I have no way of knowing what might be wrong. But you may want to see whether IPC::Open2 or IPC::Open3 could do what needs to be done -- they are part of the core distribution, and may be simpler to use than Expect.

update: one other point of confusion -- you have those two "nusmv_*" subroutines defined at the bottom of the code, but the calls to these subroutines are commented out. I suppose this is an intentional part of you debugging efforts, but if skipping those calls is part of the problem, you're the only one who can figure that out (not us); if skipping the calls has no effect on the program's behavior, why include them in the post?

---

---

Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!

Titles consisting of a single word are discouraged, and in most cases are disallowed outright.

Read Where should I post X? if you're not absolutely sure you're posting in the right place.

Please read these before you post! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

Posts may use any of the Perl Monks Approved HTML tags:

a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr

You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)

	For:		Use:
	&		&
	<		&lt;
	>		&gt;
	[		&#91;
	]		&#93;

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.