All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stas Sergeev <stssppnn@yahoo.com>
To: DOSEMU users mailing list <linux-msdos@vger.kernel.org>
Subject: Re: Dosemu 1.1.99.1 segfaults
Date: Sat, 01 Nov 2003 21:18:29 +0300	[thread overview]
Message-ID: <3FA3F8F5.1020405@yahoo.com> (raw)

Hello.

Ged Haywood wrote:
> the same version of DOS (6.22) running natively.  This seems to me to be
> a surprisingly big difference and I wonder if it means something to you.
> If you want more information can investigate more easily when I'm back
Feel free to produce a -D9+M log for the
case where it gets a stack fault. I have
no idea why this can happen. DPMI server
puts a lot of stuff on a stack, although
not on a client's stack in most cases,
but rather on a "locked" stack. But I don't
think it is some bug.

> If there's anything else you'd like me to try out on dosemu 1.3.0.0
> while I have it running on Athlon/VIA/kernel 2.6.0 please let me know.
See if the Release-1_2 branch also has
the fix you require to compile your
program. There are some patches in HEAD
that are not in Release-1_2. Make sure
they are not important for your stuff,
otherwise there is a risk you will miss
some functionality in 1.2.


             reply	other threads:[~2003-11-01 18:18 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-01 18:18 Stas Sergeev [this message]
2003-11-02 17:58 ` Dosemu 1.1.99.1 segfaults Ged Haywood
  -- strict thread matches above, loose matches on Subject: below --
2003-10-30 19:53 Stas Sergeev
2003-10-30 20:59 ` Ged Haywood
2003-10-30 21:12   ` Bart Oldeman
2003-10-30 21:30     ` Ged Haywood
2003-10-31 16:02   ` Ged Haywood
2003-10-30 18:15 Stas Sergeev
2003-10-30 18:58 ` Ged Haywood
2003-10-30 19:07   ` Bart Oldeman
2003-10-29 18:49 Stas Sergeev
2003-10-29 21:18 ` Ged Haywood
2003-10-28 16:06 Ged Haywood

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=3FA3F8F5.1020405@yahoo.com \
    --to=stssppnn@yahoo.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.