From: Jeffrey Juliano <juliano@cs.unc.edu>
To: cygwin@sources.redhat.com
Subject: Re: Invoking MODE.COM crashes cygwin bash!!! (Win95)
Date: Sun, 17 Sep 2000 06:54:00 -0000 [thread overview]
Message-ID: <2816842610.969184484@dsl-64-34-95-237.telocity.com> (raw)
In-Reply-To: <20000916185938.B12702@cygnus.com>
--On Saturday, September 16, 2000 6:59 PM -0400 Chris Faylor
<cgf@cygnus.com> wrote:
> On Sat, Sep 16, 2000 at 05:25:39PM +0200, Andreas Eibach wrote:
>> Hi there again,
>>
>> you just need to type mode.com and confirm it with return and cygwin
>> bash will crash with throwing an exception.
>
> I type "mode.com" and it gives me lots of info my com, printer, and
> console. There is no confirming with return necessary.
Chris and Andreas,
I just tried this on my win98 laptop. I got a system popup box saying
something about an illegal operation. It doesn't look like what I'm used
to seeing when an app segfaults in winNT, but for all I know this may be a
standard window for segfaults in win9x.
I dismissed the window, and my "BASH" app didn't actually die. It's still
in the task bar, and there's a dead window on the screen that won't redraw
itself or go away.
Double-clicking on the Cygwin icon on my desktop does *not* bring up a new
bash window so that I can try this again or give you cygcheck output.
...OK, I just killed WinOldApp in the "task manager", and now things seem
normal again. Let's see...strange, when I try to reproduce this by typing
mode.com in a new bash window, I get what looks like the expected output.
The first time I tried this, I had just run a fresh instance of bash while
no other cygwin apps had been running (cygwin1.dll wasn't already loaded).
Anyway, cygcyeck output is attached.
-jeff
next prev parent reply other threads:[~2000-09-17 6:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-09-16 15:51 Andreas Eibach
2000-09-16 16:00 ` Chris Faylor
2000-09-17 6:54 ` Jeffrey Juliano [this message]
2000-09-18 6:53 ` MODE.COM crashes cygwin bash!!! (Win95) ...aah GODDAMNIT....!!! Andreas Eibach
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=2816842610.969184484@dsl-64-34-95-237.telocity.com \
--to=juliano@cs.unc.edu \
--cc=cygwin@sources.redhat.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).