From: "Peter B. Steiger" <wyo_wl001@access4less.net>
To: linux-msdos@vger.kernel.org
Subject: How to debug Clipper record locking problem
Date: Mon, 19 Jul 2004 10:34:25 -0600 [thread overview]
Message-ID: <1090254865.31340.6.camel@SweetAdeline> (raw)
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
reply other threads:[~2004-07-19 16:34 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1090254865.31340.6.camel@SweetAdeline \
--to=wyo_wl001@access4less.net \
--cc=linux-msdos@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox