bash 2.05a command completion spec bug

bash 2.05a command completion spec bug

[Jason Tishler]

[-- Attachment #1: Type: text/plain, Size: 1333 bytes --]

Command completion specs causes bash 2.05a specifically *and* Cygwin
in general to behave "poorly."  By "poorly," I mean that bash becomes
unusable after attempting command completion and Cygwin cannot start
new processes:

$ ps
C:\cygwin\bin\bash.exe: *** mount table size version mismatch detected - 0x11/0x4068.
You have multiple copies of cygwin1.dll on your system.
Search for cygwin1.dll using the Windows Start->Find/Search facility
and delete all but the most recent version.  The most recent version *should*
reside in x:\cygwin\bin, where 'x' is the drive on which you have
installed the cygwin distribution.
5895398 [main] bash 1648 sync_with_child: child 1560(0x1D4) died before initialization with status code 0x1
5901389 [main] bash 1648 sync_with_child: *** child state waiting for longjmp
bash: fork: Resource temporarily unavailable

After killing all Cygwin processes, the above problem is cleared.

The problem can be reproduced by the following:

    $ # save the attachment as spec.sh
    $ . spec.sh
    $ cvs stat<TAB>
    $ # try typing some more characters

The above procedure worked fine under bash 2.05-8.

This problem seems to be reminiscent of a previous bash bug that
I reported:

    http://sources.redhat.com/ml/cygwin/2001-04/msg01560.html

Is Cygwin bash 2.05a missing any patches?

Thanks,
Jason

[-- Attachment #2: spec.sh --]
[-- Type: application/x-sh, Size: 482 bytes --]

[-- Attachment #3: Type: text/plain, Size: 214 bytes --]

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: bash 2.05a command completion spec bug

[Michael A Chase]

----- Original Message -----
From: "Jason Tishler" <jason@tishler.net>
To: "Cygwin" <cygwin@sources.redhat.com>
Sent: Tuesday, February 12, 2002 06:29
Subject: bash 2.05a command completion spec bug


> Command completion specs causes bash 2.05a specifically *and* Cygwin
> in general to behave "poorly."  By "poorly," I mean that bash becomes
> unusable after attempting command completion and Cygwin cannot start
> new processes:
>
> $ ps
> C:\cygwin\bin\bash.exe: *** mount table size version mismatch detected -
0x11/0x4068.
> You have multiple copies of cygwin1.dll on your system.
> Search for cygwin1.dll using the Windows Start->Find/Search facility
> and delete all but the most recent version.  The most recent version
*should*
> reside in x:\cygwin\bin, where 'x' is the drive on which you have
> installed the cygwin distribution.


Could you have a development version of cygwin1.dll somewhere in $PATH?

--
Mac :})
** I normally forward private questions to the appropriate mail list. **
Ask Smarter: http://www.tuxedo.org/~esr/faqs/smart-questions.htm
Give a hobbit a fish and he eats fish for a day.
Give a hobbit a ring and he eats fish for an age.



--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: bash 2.05a command completion spec bug

[Jason Tishler]

Michael,

On Tue, Feb 12, 2002 at 08:26:55AM -0800, Michael A Chase wrote:
> Could you have a development version of cygwin1.dll somewhere in $PATH?

Nope:

    $ which -a cygwin1.dll
    /usr/bin/cygwin1.dll

A Windows search comes up empty too.

Like I said in my previous post, the Cygwin problem is corrected when
all processes have exited.

Actually, I only noticed the Cygwin problem when I was writing up the
bash problem.  Nevertheless, bash 2.05a (at least the Cygwin version)
has issues with command completion specs.

Jason

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: bash 2.05a command completion spec bug

[Christopher Faylor]

On Tue, Feb 12, 2002 at 09:29:28AM -0500, Jason Tishler wrote:
>Command completion specs causes bash 2.05a specifically *and* Cygwin
>in general to behave "poorly."  By "poorly," I mean that bash becomes
>unusable after attempting command completion and Cygwin cannot start
>new processes:
>
>$ ps
>C:\cygwin\bin\bash.exe: *** mount table size version mismatch detected - 0x11/0x4068.
>You have multiple copies of cygwin1.dll on your system.
>Search for cygwin1.dll using the Windows Start->Find/Search facility
>and delete all but the most recent version.  The most recent version *should*
>reside in x:\cygwin\bin, where 'x' is the drive on which you have
>installed the cygwin distribution.
>5895398 [main] bash 1648 sync_with_child: child 1560(0x1D4) died before initialization with status code 0x1
>5901389 [main] bash 1648 sync_with_child: *** child state waiting for longjmp
>bash: fork: Resource temporarily unavailable
>
>After killing all Cygwin processes, the above problem is cleared.

Sounds like a *bad* problem with a wild pointer in bash.

Anyone interested in tracking this down with gdb?  I know that Corinna
is sort of swamped right now.

cgf

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: bash 2.05a command completion spec bug

[David Gluss]

What's a command completion spec?  Given a simple testcase,
I could look into it.
DG
----- Original Message -----
From: "Christopher Faylor" <cgf@redhat.com>
To: <cygwin@cygwin.com>
Sent: Tuesday, February 12, 2002 6:25 PM
Subject: Re: bash 2.05a command completion spec bug


> On Tue, Feb 12, 2002 at 09:29:28AM -0500, Jason Tishler wrote:
> >Command completion specs causes bash 2.05a specifically *and* Cygwin
> >in general to behave "poorly."  By "poorly," I mean that bash becomes
> >unusable after attempting command completion and Cygwin cannot start
> >new processes:
> >
> >$ ps
> >C:\cygwin\bin\bash.exe: *** mount table size version mismatch detected -
0x11/0x4068.
> >You have multiple copies of cygwin1.dll on your system.
> >Search for cygwin1.dll using the Windows Start->Find/Search facility
> >and delete all but the most recent version.  The most recent version
*should*
> >reside in x:\cygwin\bin, where 'x' is the drive on which you have
> >installed the cygwin distribution.
> >5895398 [main] bash 1648 sync_with_child: child 1560(0x1D4) died before
initialization with status code 0x1
> >5901389 [main] bash 1648 sync_with_child: *** child state waiting for
longjmp
> >bash: fork: Resource temporarily unavailable
> >
> >After killing all Cygwin processes, the above problem is cleared.
>
> Sounds like a *bad* problem with a wild pointer in bash.
>
> Anyone interested in tracking this down with gdb?  I know that Corinna
> is sort of swamped right now.
>
> cgf
>
> --
> Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
> Bug reporting:         http://cygwin.com/bugs.html
> Documentation:         http://cygwin.com/docs.html
> FAQ:                   http://cygwin.com/faq/
>


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: bash 2.05a command completion spec bug

[Christopher Faylor]

On Tue, Feb 12, 2002 at 07:09:53PM -0800, David Gluss wrote:
>What's a command completion spec?  Given a simple testcase, I could
>look into it.

Jason included everything you need to duplicate the problem in his
original message.

I haven't actually duplicated it myself since my version of cygwin is in
an iffy state right now but I trust that he's done due diligence.  He's
usually very good about that.

cgf

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/