Re: [Help-glpk] Fwd: RE: ODBC Connection to MS-Access - WHEREClause Syntaxproblems

[Alex Morelli]

Andrew / Xypron,

I'm not sure whether you wanted me to do anything further.  Here goes
anyway.  (I only didn't do this before because I didn't look very
closely at the selection options on the crash dialogue - not that I
would have known what to do.)

The error dialog also contains this:

Error signature: glpsol.exe
AppVer:0.0.0.0
Modname:ntdll.dll
ModVer:5.1.2600.5755
Offset:00010717

There was a dmp file that I tried to collect for you (attached as
xypron.bkf).  I hope I have done this correctly (I followed the
instruction here
http://blogs.msdn.com/b/jfoscoding/archive/2006/11/30/grabbing-dmp-files
-from-crash-dialogs.aspx to intercept the dmp from the crash dialog
before it disappeared -- all new to me).

I picked up the other error file from temp.  I hope the backup file (bcf
- which was originally some named .dmp file in the temp folder) is not
machine dependent.

Regards, Alex 



-----Original Message-----
From: Andrew Makhorin [mailto:address@hidden 
Sent: Thursday, 30 June 2011 4:44 AM
To: Xypron
Cc: address@hidden; Alex Morelli
Subject: Re: Fwd: RE: [Help-glpk] ODBC Connection to MS-Access -
WHEREClause Syntaxproblems

Hi Xypron,

> Alex experiences a return code indicating a memory access error after
> glpsol --check
> writes
> Model has been successfully generated
> to the console.
> 
> Do you have an idea how to identify the cause.
> 
> The glpsol dll and executable are those of Gusek 0.2.12, which are the
> same ones
> that I published as GLPK for Windows 4.45.
> 

I need more detailed information to identify the error; the status code
is not sufficient. Under MS Windows in the case of segmentation fault
(access violation) there should appear an error window indicating some
information, in particular, the module/dll, where the exception
happened, context, fault instruction address, stack dump, etc. Though it
would be better to compile and run glpsol in a debug mode. Please note
that if --check was specified and the model was successfully processed,
the error may happen only in few routines called below a statement
labelled 'done' (see src/glpapi19.c).


Andrew Makhorin

f995_appcompat.txt
Description: f995_appcompat.txt

xypron.bkf
Description: xypron.bkf