From: drevil@warpcore.org
To: "John J. Boyer" <director@chpi.org>
Cc: linux-msdos@vger.kernel.org
Subject: Re: Strange dosemu behavior.
Date: Thu, 9 May 2002 13:43:37 -0500 [thread overview]
Message-ID: <20020509184337.GA19300@virtucon.warpcore.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0205091050580.2428-100000@Jumbo>
On Thu, May 09, 2002 at 11:01:45AM -0500, John J. Boyer wrote:
> This kind of behavior usually means that the program has crashed by
> trying to write outside of the memory it has been alotted, performing an
> illegal operation, etc. I've seen it quite often.
> John
Is there any way I can get some debug output? This obviously works a-ok on a
"real" dos system. Since it's a bug, i'd like to fix it. dosemu is the one
spontaneously closing though, there's no segfault in the console where I started
it, so I assume dosemu is just dying. Any devel or other person that can tell
me how I can debug this?
-shawn
> On Thu, 9 May 2002
> drevil@warpcore.org wrote:
>
> > I've tried one of the stable releases of dosemu, and the latest developer
> > release available from the dosemu.org page and I'm having the same problem. The
> > problem is this:
> >
> > running decsent2's setup program to install it
> >
> > it starts up, I get the rational dos/4gw banner
> > it plays the test movie says I passed (it runs really great too!)
> > then it asks me for which install option I want, crazy, large, etc.
> > when I select one of the install options the xdosemu window that was
> > opened up spontaneously closes with no error or failure log that I can see.
> >
> > Any ideas?
> >
> > -shawn
next prev parent reply other threads:[~2002-05-09 18:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-09 15:18 Strange dosemu behavior drevil
2002-05-09 16:01 ` John J. Boyer
2002-05-09 18:43 ` drevil [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-05-09 20:22 Stas Sergeev
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=20020509184337.GA19300@virtucon.warpcore.org \
--to=drevil@warpcore.org \
--cc=director@chpi.org \
--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