RE: [Axiom-developer] Axiom crashing in Zope-Plone

[Bill Page]

Hans,

When you can find some "spare" time, would it be possible for
you to attempt what Camm describes below?

Camm,

I suppose that "setting TERM environment variable to dumb"
must disable GCL's use of readline? If so, since we definitely
don't want readline functionality when AXIOMsys is called
from the MathAction wiki, I can easily set this environment
variable when AXIOMsys is called.

Thanks!

Bill Page.

On Friday, October 01, 2004 11:44 AM you wrote:
> 
> "Page, Bill" <address@hidden> writes:
> 
> > Cam,
> > 
> > The original report from Hans:
> > 
> >   
> http://lists.gnu.org/archive/html/axiom-developer/2004-09/msg0
> 0056.html
> > 
> > referred to what later was discovered to be a seg fault
> > (EXITSTATUS:139 from Python 2.2 popen3) generated by Axiom
> > when run as a sub-process (popen3). Hans later reported that
> > the failure occured while running a debian binary version
> > of Axiom on an Intel i386 box.
> > 
> 
> My suspicion lies in python's pipe code, possibly in conjunction with
> GCL readline.  Can a segault be reproduced with axiom intel
> standalone?  Alternatively, can someone please try to reproduce
> setting the TERM environment variable to "dumb"?  Might need to check
> strace -f on the process to make sure Python does not setup the pipe
> environment as a readline capable terminal (e.g. vt100).  If one can
> get to axiom at all over the pipe, try doing )lisp (si::readline-off)
> at the beginning, or putting this into some axiom rc startup file or
> something. 
> 
> Please feel free to report all Debian binary bugs to the Debian BTS
> via 'reportbug'.