From: ericblake@comcast.net (Eric Blake)
To: "clones everywhere" <cygwin-talk@cygwin.com>
Subject: Re: 1.5.20: Occasional crash at address 0x6100365f (cygthread::stub() in cygthre
Date: Fri, 21 Jul 2006 00:36:00 -0000 [thread overview]
Message-ID: <072120060036.29340.44C0219F000AE56F0000729C22135753330A050E040D0C079D0A@comcast.net> (raw)
> I'm not sure what this means. If bash kept running then that would
> indicate that it isn't the bash which is crashing. Possibly a forked
>
> cgf
> copy is crashing.
Hmmm, I wish I could fork, and make myself twice as productive
(of course, I hope my fork would be a bit more robust than
cgf's, because I don't want to crash)
reply other threads:[~2006-07-21 0:36 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=072120060036.29340.44C0219F000AE56F0000729C22135753330A050E040D0C079D0A@comcast.net \
--to=ericblake@comcast.net \
--cc=cygwin-talk@cygwin.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).