Re: [Help-glpk] Thread safety of GLPK
Hello Paul, I'd like to know if GLPK (the C lib) is not thread safe? Request for thread safety have been recurring: http://lists.gnu.org/archive/html/help-glpk/2002-08/msg00011.html http://lists.gnu.org/archive/html/help-glpk/2003-10/msg00020.html http://lists.gnu.org/archive/html/help-glpk/2005-04/msg00027.html http://lists.gnu.org/archive/html/help-glpk/2007-08/msg00040.html http://lists.gnu.org/archive/html/help-glpk/2009-03/msg00049.html http://lists.gnu.org/archive/html/help-glpk/2009-07/msg0.html Please, read the thread starting at http://lists.gnu.org/archive/html/help-glpk/2009-07/msg0.html It indicates some of the areas that make GLPK not threadsafe. Best regards Xypron -- GRATIS für alle GMX-Mitglieder: Die maxdome Movie-FLAT! Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01 ___ Help-glpk mailing list Help-glpk@gnu.org http://lists.gnu.org/mailman/listinfo/help-glpk
Re: [Help-glpk] Thread safety of GLPK
I #8217;d like to know if GLPK (the C lib) is not thread safe? No, glpk is not thread safe. If not, are there any plans to ever make it thread safe? We get occasional core dumps in a multi-threaded environment which we think are related to thread safety as we get a SIGSEGV inside GLPK. Thread safety (unlike re-enterability) requires locking/unlocking program objects used by concurrent threads. Since the standard C does not provide such a feature, there are no plans in this direction. I'm just wondering how you would use glpk if it were thread safe? Thanks. Andrew Makhorin ___ Help-glpk mailing list Help-glpk@gnu.org http://lists.gnu.org/mailman/listinfo/help-glpk
