public inbox for linux-msdos@vger.kernel.org
 help / color / mirror / Atom feed
From: "anon permutation" <anonpermutation@hotmail.com>
To: nemesis-lists@icequake.net
Cc: linux-msdos@vger.kernel.org
Subject: Re: Dos App hangs with msg X: expose event
Date: Tue, 07 Sep 2004 07:45:03 +0000	[thread overview]
Message-ID: <BAY15-F21KRfcjcMzfo000385c0@hotmail.com> (raw)



Hi Ryan,

I have posted the bug on sourceforge.  Please take a look.  Thank you for 
helping out.

I have encoutered problems while uploading even 256KB chunks, as a result, I 
have only pasted the top and bottom of my log online.  The complete log is 
about 23MB.  Is there a place where I can email you the file?

If the GP fault from run_vm86() is ok, does that mean I can just change the 
codes that handle the fault in vm_86_GP_fault() to do nothing?  Would that 
allow me to work around the problem?


Alvin



>From: Ryan Underwood <nemesis-lists@icequake.net>
>To: linux-msdos@vger.kernel.org
>Subject: Re: Dos App hangs with msg X: expose event
>Date: Mon, 6 Sep 2004 20:39:02 -0500
>
>
>On Tue, Sep 07, 2004 at 01:06:50AM +0000, anon permutation wrote:
> >
> > Thank you for your reply.  The Dos app requires a hardware key and 
>cannot
> > be downloaded from the Internet.
>
>Doh. Well, maybe the developer of the application has an idea why it
>doesn't work.
>
> > I tried attaching GDB to the hang xdosemu process, and I got the 
>following
> > Back Trace:
> >
> > 0x401cf06d in syscall() from /lib/libc.so.6
> > 0x080936a3 in run_dpmi() at dpmi.c:2317
> > 0x080948d2 in dpmi_init() at dpmi.c:2727
> > 0x080970eb in dpmi_readmode_hlt (line=0xfc807 <repeats 197 times> ...) 
>at
> > dpmi.c:3710
> > 0x0808b76d in vm_86_GP_fault() at do_vm86.c:311
> > 0x0808bc01 in run_vm86() at do_vm86.c:440
> > 0x0808bd5e in loopstep_run_vm86() at do_vm86.c:496
> > 0x0804cfc6 in main(argc=2, argv=0xbffffd14) at emu.c:398
> >
> > It seems like although dosemu continues to response, a General 
>Protection
> > Fault has already happened.
>
>GP faults are ok as long as they are coming from the V86 process.  A GP
>fault in the 32-bit dosemu code would be a problem.
>
> > Any ideas?  What other information can I provide you?
>
>You could provide a log by running dosemu -D9+a -o /tmp/log and posting
>the log on dosemu.sf.net bug tracker.  You will have to split it into
>256KB chunks or the file upload is not accepted.
>
>--
>Ryan Underwood, <nemesis@icequake.net>
>-
>To unsubscribe from this list: send the line "unsubscribe linux-msdos" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at  http://vger.kernel.org/majordomo-info.html

_________________________________________________________________
Don’t just search. Find. Check out the new MSN Search! 
http://search.msn.click-url.com/go/onm00200636ave/direct/01/


             reply	other threads:[~2004-09-07  7:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-07  7:45 anon permutation [this message]
2004-09-08  4:34 ` Dos App hangs with msg X: expose event Ryan Underwood
  -- strict thread matches above, loose matches on Subject: below --
2004-09-07  1:06 anon permutation
2004-09-07  1:39 ` Ryan Underwood
2004-08-30  5:54 anon permutation
2004-09-06  6:12 ` Ryan Underwood

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=BAY15-F21KRfcjcMzfo000385c0@hotmail.com \
    --to=anonpermutation@hotmail.com \
    --cc=linux-msdos@vger.kernel.org \
    --cc=nemesis-lists@icequake.net \
    /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