2012/11/27 Jean-Pierre Flori <jpfl...@gmail.com>: > OK I think I got it. > The culprit is commit 880259cb5533913a6c09d6c99d8d26a22e1b9195. > > I hirst thought that the following change was to be blamed: > --- a/src/c/main.d > +++ b/src/c/main.d > @@ -77,7 +77,7 @@ > 1, /* ECL_OPT_TRAP_SIGCHLD */ > 1, /* ECL_OPT_TRAP_INTERRUPT_SIGNAL */ > 1, /* ECL_OPT_SIGNAL_HANDLING_THREAD */ > - 128, /* ECL_OPT_SIGNAL_QUEUE_SIZE */ > + 16, /* ECL_OPT_SIGNAL_QUEUE_SIZE */ > 0, /* ECL_OPT_BOOTED */ > 8192, /* ECL_OPT_BIND_STACK_SIZE */ > 128, /* ECL_OPT_BIND_STACK_SAFETY_AREA */ > but changing this back in git HEAD from some time yesterday does not > fix the issue. > > (By the way, not sure why we don't use threaded ECL in Sage, I guess > that our current signal handling would be completely broken as a first > good enough reason, not really sure there are other reasons.) > > Best, > > > > -- > Jean-Pierre Flori
I had to backport patches to be able to build ECL at revision 880259cb5533913a6c09d6c99d8d and some previous ones between 880259cb5533913a6c09d6c99d8d and released version 12.2.1, I hope I did this right and 880259cb5533913a6c09d6c99d8d is indeed the culprit, but the commits I imported back mainly concern functions involving directories management and the conditional definition and use of SPINLOCK depending on ECL_THREADS in very few places, so it looks ok. -- Jean-Pierre Flori ------------------------------------------------------------------------------ Monitor your physical, virtual and cloud infrastructure from a single web console. Get in-depth insight into apps, servers, databases, vmware, SAP, cloud infrastructure, etc. Download 30-day Free Trial. Pricing starts from $795 for 25 servers or applications! http://p.sf.net/sfu/zoho_dev2dev_nov _______________________________________________ Ecls-list mailing list Ecls-list@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ecls-list