From: Christopher Faylor <cgf-use-the-mailinglist-please@cygwin.com>
To: cygwin-talk@cygwin.com
Subject: Re: fresh 1.7, bash fails with STATUS_ACCESS_VIOLATION
Date: Mon, 06 Jul 2009 01:48:00 -0000 [thread overview]
Message-ID: <20090706014808.GA3799@ednor.casa.cgf.cx> (raw)
In-Reply-To: <4A51553C.3080406@gmail.com>
On Mon, Jul 06, 2009 at 02:37:00AM +0100, Dave Korn wrote:
>Vincent R. wrote:
>>bash 3.2.49-22 OK
>>libreadline6 5.2.14-12 OK
>>libreadline7 6.0.3-1 OK
>
>Jerry DeLisle wrote:
>
>>bash 3.2.49-22
>>libreadline6 5.2.14-12
>>libreadline7 6.0.3-1
>
>Err, ok. So you've got the working versions. So why do you think
>you're getting the same bug at all?
>
>Surely this *has* to be some entirely different issue than the one
>that's breaking a version of bash that you aren't using on a version of
>windows that you aren't using?
Personally, I blame binutils. There was always something
not-quite-right about those programs. For instance, I don't like the
way they objectify some source code. If the programs weren't running on
a PC, I'd say they were definitely non-PC.
cgf
parent reply other threads:[~2009-07-06 1:48 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <4A51553C.3080406@gmail.com>]
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=20090706014808.GA3799@ednor.casa.cgf.cx \
--to=cgf-use-the-mailinglist-please@cygwin.com \
--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).