From: "?????? ????????" <vargulin@rambler.ru>
To: linux-msdos@vger.kernel.org
Subject: Re: DOSEmu has crashed while calling INT 3!
Date: Sun, 08 Nov 2009 19:53:50 +0200 [thread overview]
Message-ID: <4AF705AE.9040004@rambler.ru> (raw)
In-Reply-To: <c3d607cc0911080910y2767864bq3ca3a7a773d60216@mail.gmail.com>
Bart Oldeman ???????(??):
> On Sun, Nov 8, 2009 at 11:55 AM, ?????? ???????? <vargulin@rambler.ru> wrote:
>
>> Paul Lagasse ???????(??):
>>
>>> ?????? ???????? wrote:
>>>
>>>> (I have DOSEmu 1.4 in Ubuntu Linux 9.10), DOSEmu has crashed
>>>>
>>> Does the problem occur in Ubuntu 9.04? I've had things crash in 9.10 that
>>> don't crash in earlier Ubuntu releases.
>>>
>>>
>> Yes, problem has occur in the Ubuntu 9.04. In the Ubuntu 8.04 and 8.10 (with
>> DOSEmu 1.2 and DOSEmu 1.3) problem does not exist.
>>
>
> How did dosemu crash? Do you see a trace in ~/.dosemu/boot.log?
> It might actually be a kernel bug, if dosemu crashes with a plain
> "segmentation fault", and if you run "dmesg" after, which says
> something like:
>
> --May 22 16:47:47 localhost kernel: note: dosemu.bin[5281] exited with
> preempt_count 1
>
> I attempted to fix the issue in the kernel but there was a problem
> with the patch -- I'll revisit when I have time.
> A workaround is using $_cpu_emu="vm86" or recompiling the kernel with
> preemption disabled.
>
> Bart
> I see the boot.log on the DOSEmu directory. In these file does not contain "segmentation fault" or "
>
I see the boot.log on the DOSEmu directory. In these file does not
contain "segmentation fault". I can sent to someone of Your's Turbo.Exe,
Turbo.Tpl and Hello.pas for make an experiment with these shitted bug.
For experiment, please download the Ubuntu 9.10 ISO image, and boot from
it, written to the CD disk, and after booting from it, install the
official dosemu package (with dosemu 1.4) and download the my package
with turbo.exe, turbo.tpl and hello.pas, and in the dosemu go to
directory contain these files and run the turbo.exe and press F9 and
twice press the F7 or F8 key for get this ugly bad bug. These file
package at: http://www.sendspace.com/file/b6mq0j (238 KB). Deletion link
is:
http://www.sendspace.com/delete/b6mq0j/538417c630a0d4cf233e8f86f76d6d11.
Enjoy.
next prev parent reply other threads:[~2009-11-08 17:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-06 19:30 DOSEmu has crashed while calling INT 3! ?????? ????????
2009-11-06 23:38 ` John Coppens
[not found] ` <4AF4BB60.60806@sbcglobal.net>
2009-11-07 0:21 ` DOSEmu has crashed while calling INT3! John Coppens
2009-11-07 21:01 ` DOSEmu has crashed while running debugging ?????? ????????
2009-11-07 21:29 ` DOSEmu has crashed while calling INT 3! ?????? ????????
[not found] ` <4AF5F28A.5060503@sbcglobal.net>
2009-11-08 17:20 ` ?????? ????????
[not found] ` <4AF5E993.8090601@comcast.net>
2009-11-08 16:55 ` ?????? ????????
2009-11-08 17:10 ` Bart Oldeman
2009-11-08 17:53 ` ?????? ???????? [this message]
2009-11-08 17:58 ` Bart Oldeman
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=4AF705AE.9040004@rambler.ru \
--to=vargulin@rambler.ru \
--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.