<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 6/9/2012 3:46 AM, NEETI SONTH wrote:<br>
</div>
<blockquote
cite="mid:CABtJOhKiitPH9cJHcrBtNyAzh5kM6bFSB+GssJ_413KWnsyhrA@mail.gmail.com"
type="cite"><br>
<br>
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
<div>
<div>
<blockquote type="cite">Hi.</blockquote>
</div>
</div>
</div>
</blockquote>
</div>
</blockquote>
<div>When I run the command 'lattice-tool -max-time 4
-write-ngrams <filename> -in-lattice-list
<filename2>'</div>
<div> the command limits the maximum time of operation for
just the first lattice file in the list of lattice files. For
remaining lattice-files, it doesnt limit the time of
operation. The command says "LIMITS THE MAXIMUM TIME OF
OPERATION PER LATTICE" ... So why isnt it doing so???</div>
<div><br>
</div>
<div>thanks.</div>
<div>Neeti Sonth</div>
</div>
<br>
</blockquote>
<br>
It seems that in Linux and compatible systems, unlike in Solaris,
where the code was originally developed, the SIGALRM handler needs
to use sigsetjmp/siglongjmp() instead of just plain setjmp/longjmp,
or else subsequent alarms won't invoke the handler due to signal
mask modification. The effect was that lattice-tool -timeout would
work only for the first lattice triggering the timeout on Linux and
Cygwin systems.<br>
<br>
The attached patch should fix the problem.<br>
<br>
Andreas<br>
<br>
<br>
<br>
</body>
</html>