* How to debug Clipper record locking problem
@ 2004-07-19 16:34 Peter B. Steiger
0 siblings, 0 replies; only message in thread
From: Peter B. Steiger @ 2004-07-19 16:34 UTC (permalink / raw)
To: linux-msdos
I just installed 1.3.1 including all CVS updates as of 2004-07-18 and
tested my Clipper application. A problem still exists when it tries to
lock a single DBF record in protected mode (DPMI memory=14MB). When it
issues the dbrlock() function, requesting that a single record be
locked, the application freezes as though in an infinite loop. I must
use dosdebug or kill the process to escape.
Strangely, if I use freedos the problem does not occur. Only when I use
an existing Win98 or DOS 6.22 partition can I recreate the problem.
Also, if I write a simple test program that only issues the dbrlock()
function request, it works fine... the error only occurs with my 4-MB
EXE.
What debug flags should I use to isolate the problem? If I turn on all
flags, the resulting output is several million bytes long.
-------
Peter B. Steiger
Cheyenne, WY
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2004-07-19 16:34 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2004-07-19 16:34 How to debug Clipper record locking problem Peter B. Steiger
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox