From: John Coppens <john@jcoppens.com>
To: Mike McCarty <Mike.McCarty@sbcglobal.net>
Cc: linux-msdos@vger.kernel.org
Subject: Re: DOSEmu has crashed while calling INT3!
Date: Fri, 6 Nov 2009 21:21:08 -0300 [thread overview]
Message-ID: <20091106212108.f2a1ef09.john@jcoppens.com> (raw)
In-Reply-To: <4AF4BB60.60806@sbcglobal.net>
On Fri, 06 Nov 2009 18:12:16 -0600
Mike McCarty <Mike.McCarty@sbcglobal.net> wrote:
> > If, using TP 7, and using F7, you have a crash, then look at the code
> > you are executing. It's unlikely to be DOSEMU's fault. I've used F7
> > many times.
>
> Very possibly the case. More than one assembly program has overwritten
> important code or data areas, including interrupt vectors. :-)
>
> In any case, without more information, and experimentation, it's
> impossible to know what's gone wrong. I wonder if he could try
> an experiment with a small program which simply comprises a bunch
> of NOPs and then try the F7 trick, and then try inserting an INT3
> in the middle of his NOPs. If this works, then he's almost surely
> looking for a defect in his own code, and not with DOSEMU.
I agree, but the solution is not yelling "Please fix these bug!"
Thanks for your help helping the OP.
John
next prev parent reply other threads:[~2009-11-07 0:21 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 ` John Coppens [this message]
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 ` ?????? ????????
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=20091106212108.f2a1ef09.john@jcoppens.com \
--to=john@jcoppens.com \
--cc=Mike.McCarty@sbcglobal.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