[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Help-glpk] Re: Help-glpk Digest, Vol 86, Issue 32

From: Sylvain Fournier
Subject: [Help-glpk] Re: Help-glpk Digest, Vol 86, Issue 32
Date: Mon, 25 Jan 2010 09:14:00 -0200

Thanks Xypron and Andrew for solving my problem! This new error routine will be a good reason for me to upgrade my GLPK version. :-)


Date: Sun, 24 Jan 2010 07:55:22 +0300
From: Andrew Makhorin <address@hidden>
Subject: Re: [Help-glpk] Application crash due to assert in GLPK
To: xypron <address@hidden>
Cc: address@hidden
Message-ID: <address@hidden>
Content-Type: text/plain; charset=us-ascii

> Unfortunately a failed xassert will completely stop the program that
> called the glpk native library. With the current design it is not
> possible to catch a Java exception.

> I wonder if it was wise to put an assert here since GLPK should not
> fail due to a change the system time.

> Hence I suggest Andrew could remove the assert in function x_time.

I replaced the old version of xtime by a new one, which does not call
xassert. The new version is configurable and attempts to use a native
time function, for example, gettimeofday on POSIX platforms. I also
added a new api routine glp_error_hook to install a user-defined hook
routine called from xerror before the latter calls abort; this feature
can be used to prevent abnormal termination caused by glpk api.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]