The 15_security/20_cli.y test has been broken for quite sometime, and I
finally got around to fixing it, since I NEED to test the CLI logic, after
totally reworking the code. I addresses the obvious issue (we always
skipped the last 4 tests), and now I've got a VERY strange problem that has
me stumped (been awhile...)
There are four tests that use expect, and they are almost identical. The
first one works fine, the second fails, and after tossing syslog calls into
the code, I have tracked the problem to here: in EFS/CLI.pm, in
query_password, I have:
EFS::Syslog->message( q{info}, q{Calling read_password} );
my $authpass = q{};
eval { $authpass = read_password($args{prompt}) };
EFS::Syslog->message( q{info}, q{Eval is done} );
my $eval_error = $EVAL_ERROR;
if ( $eval_error ) {
EFS::Syslog->message( q{err}, q{Failed to read password:
$eval_error} );
}
elsif ( not $authpass ) {
EFS::Syslog->message( q{info}, q{Null password} );
}
else {
EFS::Syslog->message( q{info}, q{Successfully read password} );
}
The "Eval is done" message NEVER shows up, and the process is dying at that
point. I am about to resort to stracing the process, but under what
situation does eval NOT trap an exception?
Suggestions?
_______________________________________________
EFS-dev mailing list
[email protected]
http://mailman.openefs.org/mailman/listinfo/efs-dev
