* Re: fresh 1.7, bash fails with STATUS_ACCESS_VIOLATION
[not found] ` <4A51553C.3080406@gmail.com>
@ 2009-07-06 1:48 ` Christopher Faylor
0 siblings, 0 replies; only message in thread
From: Christopher Faylor @ 2009-07-06 1:48 UTC (permalink / raw)
To: cygwin-talk
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
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2009-07-06 1:48 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <4A51008E.9050205@verizon.net>
[not found] ` <4A51553C.3080406@gmail.com>
2009-07-06 1:48 ` fresh 1.7, bash fails with STATUS_ACCESS_VIOLATION Christopher Faylor
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).