#13211: Upgrade GAP to 4.5.6
-----------------------------------------------------------+----------------
       Reporter:  kini                                     |         Owner:  
tbd              
           Type:  enhancement                              |        Status:  
needs_work       
       Priority:  major                                    |     Milestone:  
sage-5.5         
      Component:  packages                                 |    Resolution:     
              
       Keywords:                                           |   Work issues:     
              
Report Upstream:  Completely fixed; Fix reported upstream  |     Reviewers:  
Dmitrii Pasechnik
        Authors:  Volker Braun                             |     Merged in:     
              
   Dependencies:  #13123, #13579                           |      Stopgaps:     
              
-----------------------------------------------------------+----------------

Comment (by dimpase):

 Replying to [comment:165 jdemeyer]:
 > Now that I know what the problem is, reproducing the Segmentation Fault
 is trivial. Within a Sage shell:
 > {{{
 > (sage-sh) jdemeyer@sage:sage-5.5.beta2$ gap &>/dev/full
 > Segmentation fault
 > }}}
 This is not the complete story. First off, you need to run with -T, which
 is meant to suppress the usual interactive behavour, and this is the
 option using which the orphans in question arise. In fact, it is because
 {{{stderr}}} is full, not because {{{stdout}}} is full.
 {{{
 (sage-sh) dima@sage$ gap -T >/dev/full
 Error, Cannot write to file descriptor 1, see 'LastSystemError();'

 Error, Cannot write to file descriptor 1, see 'LastSystemError();'

 Error, Cannot write to file descriptor 1, see 'LastSystemError();'

 Error, Cannot write to file descriptor 1, see 'LastSystemError();'

 Error, Cannot write to file descriptor 1, see 'LastSystemError();'

 Syntax error: ; expected
 ^
 Error, Cannot write to file descriptor 1, see 'LastSystemError();'

 (sage-sh) dima@sage$
 }}}
 Thus if the {{{stderr}}} is OK, it sort of works (the {{{Syntax error;}}}
 is quite weird though, and might be an indication of a "more real" bug).
 By the way, {{{gap-4.4}}} just hangs in this situation.

 As we talk about the situation with -T on, we can patch, say,
 {{{ErrorQuit}}} for this case to print to {{{stderr}}} and quit
 immediately. This will not fix this completely, but at least it will make
 sure that with -T option the behaviour is as it should be.

 An alternative is to change Sage so that GAPs {{{stderr}}} does not get
 redirected. I don't know how well this will work, though.

-- 
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/13211#comment:170>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica, 
and MATLAB

-- 
You received this message because you are subscribed to the Google Groups 
"sage-trac" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/sage-trac?hl=en.

Reply via email to