Hello,
I'm currently writing an interface between glpk and scilab (see
http://www.scilab.org).
My interface is working fine, but for some problems, glpk emits an
assert which made scilab to hangs.
I have seen a preceding post where somebody adviced to catch the ABORT
signal to avoid the hang
> I'm currently writing an interface between glpk and scilab (see
> http://www.scilab.org).
> My interface is working fine, but for some problems, glpk emits an
> assert which made scilab to hangs.
> I have seen a preceding post where somebody adviced to catch the ABORT
> signal to avoid the hang
Hi all
Andrew Makhorin recently wrote:
> As to catching the xassert message, you can use glp_term_hook;
> all glpk terminal output goes through it.
Some comments on 'glp_term_hook' and C++.
With regard to the following section in the 4.28 manual:
3.3.4 Install hook to intercept terminal
It is an issue. Xassert means the same as assert, i.e. if it is
invoked, something is going wrong, and a most relevant action in
this case is to abnormally terminate the program, because some glpk
data structures (as well as other memory data) may be damaged, and
further execution of the program
