Re: 1.7.7: 'Bad address' errors when using Windows 2003 R2 WOW64

[Gerry Reno <greno@verizon.net>]

On 02/08/2011 04:10 PM, Gerry Reno wrote:
> On 02/08/2011 03:28 PM, Gerry Reno wrote:
>   
>> On 02/08/2011 03:14 PM, Larry Hall (Cygwin) wrote:
>>   
>>     
>>> On 2/8/2011 2:47 PM, Gerry Reno wrote:
>>>
>>> <snip>
>>>
>>>     
>>>       
>>>> As you can see it is not just the lapack0.sh file in /etc/profile.d/.
>>>> Even when I remove lapack0.sh the problem just moves to another file.
>>>>
>>>> And the problem is not consistent except when I try to run bash as a
>>>> login shell and there it occurs without fail for some reason.
>>>>       
>>>>         
>>> <snap>
>>>
>>> Does reverting bash to V3 change anything?
>>>
>>>     
>>>       
>> It changes slightly.  I don't see the "Bad address" but more segfaults:
>>
>>     bash-3.2$ (for p in $(ls /etc/profile.d/*.sh); do . $p;done)
>>     bash-3.2$ (for p in $(ls /etc/profile.d/*.sh); do . $p;done)
>>     bash-3.2$ (for p in $(ls /etc/profile.d/*.sh); do . $p;done)
>>     bash-3.2$ (for p in $(ls /etc/profile.d/*.sh); do . $p;done)
>>     bash-3.2$ (for p in $(ls /etc/profile.d/*.sh); do . $p;done)
>>     Segmentation fault (core dumped)
>>     bash-3.2$ (for p in $(ls /etc/profile.d/*.sh); do . $p;done)
>>     bash-3.2$ (for p in $(ls /etc/profile.d/*.sh); do . $p;done)
>>     bash-3.2$ (for p in $(ls /etc/profile.d/*.sh); do . $p;done)
>>     bash-3.2$ (for p in $(ls /etc/profile.d/*.sh); do . $p;done)
>>     bash-3.2$ (for p in $(ls /etc/profile.d/*.sh); do . $p;done)
>>     bash-3.2$ (for p in $(ls /etc/profile.d/*.sh); do . $p;done)
>>     bash-3.2$ (for p in $(ls /etc/profile.d/*.sh); do . $p;done)
>>     Segmentation fault (core dumped)
>>     bash-3.2$ (for p in $(ls /etc/profile.d/*.sh); do . $p;done)
>>     bash-3.2$ (for p in $(ls /etc/profile.d/*.sh); do . $p;done)
>>     bash-3.2$ (for p in $(ls /etc/profile.d/*.sh); do . $p;done)
>>     bash-3.2$ (for p in $(ls /etc/profile.d/*.sh); do . $p;done)
>>     bash-3.2$ (for p in $(ls /etc/profile.d/*.sh); do . $p;done)
>>     bash-3.2$ (for p in $(ls /etc/profile.d/*.sh); do . $p;done)
>>     bash-3.2$ (for p in $(ls /etc/profile.d/*.sh); do . $p;done)
>>
>>
>> And I still get postinstall issues:
>>
>>     Package: bash
>>             bash.sh exit code 128
>>     Package: xorg-server
>>             xorg-server.sh exit code 128
>>     Package: Unknown package
>>             coreutils.sh exit code 128
>>             libglade2.0.sh exit code 2
>>
>>
>>
>> Regards,
>> Gerry
>>
>>
>>   
>>     
> Some further testing shows that I can still generate "Bad address" errors:
>
>     bash-3.2$ (for p in $(ls /etc/profile.d/*.sh); do . $p;done)
>     bash-3.2$ (for p in $(ls /etc/profile.d/*.sh); do . $p;done)
>     bash-3.2$ (for p in $(ls /etc/profile.d/*.sh); do . $p;done)
>     bash: /etc/profile.d/lapack0.sh: Bad address
>     bash-3.2$
>
>
>
>   

And today I still see some odd things happening even after going back to
bash v3:

    bash-3.2$ whoami
    ip-0a7a25a3\administrator
    bash-3.2$
    bash-3.2$ /bin/bash -i
    bash-3.2$ exit
    exit
          2 [main] bash 1224 sig_send: wait for sig_complete event
    failed, signal -3
    4, rc -1, Win32 error 5
          2 [main] bash 1224 sig_send: wait for sig_complete event
    failed, signal -3
    4, rc -1, Win32 error 5
    Segmentation fault
    bash-3.2$


Regards,
Gerry


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple