From: Gerry Reno <greno@verizon.net>
To: cygwin@cygwin.com
Subject: Re: 1.7.7: 'Bad address' errors when using Windows 2003 R2 WOW64
Date: Tue, 08 Feb 2011 20:28:00 -0000 [thread overview]
Message-ID: <4D51A756.2040507@verizon.net> (raw)
In-Reply-To: <4D51A409.7020801@cygwin.com>
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
--
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
next prev parent reply other threads:[~2011-02-08 20:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-07 18:19 Gerry Reno
2011-02-07 19:52 ` marco atzeri
2011-02-07 20:07 ` Gerry Reno
2011-02-07 20:32 ` marco atzeri
2011-02-08 19:48 ` Gerry Reno
2011-02-08 20:14 ` Larry Hall (Cygwin)
2011-02-08 20:28 ` Gerry Reno [this message]
2011-02-08 21:10 ` Gerry Reno
2011-02-09 17:44 ` Gerry Reno
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=4D51A756.2040507@verizon.net \
--to=greno@verizon.net \
--cc=cygwin@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).