Dear Dima,
thank you for your message. In the next release of the GAP system
both LogTo and InputLogTo must recover properly from the break loop
in case of trying to create a log file in a non-accessible place.
Best wishes,
Alexander
On 16 Oct 2008, at 09:40, Asst. Prof. Dmitrii (Dima) Pasechnik wrote:
Dear all,
on Linux an attempt to LogTo to a place that is not accessable results
in logging being deadlocked:
LogTo(); results in
LogTo: can not close the logfile at, and inability to start logging
at all.
Example:
gap> LogTo("blah/blah"); # directory "blah" does not exist, no
wonder...
LogTo: cannot log to blah/blah at
LOG_TO( name );
called from
<function>( <arguments> ) called from read-eval-loop
Entering break read-eval-print loop ...
you can 'quit;' to quit to outer loop, or
you can 'return;' to continue
brk> # ^D pressed, then:
gap> LogTo();
LogTo: can not close the logfile at
CLOSE_LOG_TO( );
gap> LogTo("blah");
#I Already logging to blah/blah
gap>
(needless to say, the file "blah" isn't even created)
Same applies to InputLogTo.
Thanks for attention to this,
Dima
_______________________________________________
Forum mailing list
[email protected]
http://mail.gap-system.org/mailman/listinfo/forum
_______________________________________________
Forum mailing list
[email protected]
http://mail.gap-system.org/mailman/listinfo/forum
