2009/7/5 Sylvain Pasche:
> (by the way, I recently discovered MinTTY and I'm pretty impressed. MinTTY +
> screen offers a very nice multiple-tab environment on Cygwin).
Thanks!
Btw, you can enable browser-style tab switching with (Shift+)Ctrl+Tab
by mapping MinTTY's keycodes for those in .screenr
On Sun, Jul 05, 2009 at 10:04:42PM -0700, Ian Kelling wrote:
>Christopher Faylor wrote:
>>It sounds like you are conflating a serious STATUS_ACCESS_VIOLATION
>>which is known to occur on Windows 7 with your not-so-serious "Bash
>>initialization w/cygwin-1.7".
>
>not-so-serious? Cygwin 1.7 install
Christopher Faylor wrote:
It sounds like you are conflating a serious STATUS_ACCESS_VIOLATION which
is known to occur on Windows 7 with your not-so-serious "Bash
initialization w/cygwin-1.7".
not-so-serious? Cygwin 1.7 install is very broken because of this bug. Seems
serious to me. Is anyone
Jerry DeLisle wrote:
I am very happy to accept that this problem is something else. Vincent
sent a note that it is working for him. I am not sure what "working"
means. I have a bash prompt, but none of the default environment
variables such as prompts and paths and setting up the home direct
Christopher Faylor wrote:
On Mon, Jul 06, 2009 at 05:20:41AM +0100, Dave Korn wrote:
Jerry DeLisle wrote:
I am making the switch to 1.7. I started with a clean windows (nt4)
environment and went through the usual run of setup-1.7 downloaded today.
All appears fine, but bash does not get initi
On Mon, Jul 06, 2009 at 05:20:41AM +0100, Dave Korn wrote:
>Jerry DeLisle wrote:
>> I am making the switch to 1.7. I started with a clean windows (nt4)
>> environment and went through the usual run of setup-1.7 downloaded today.
>>
>> All appears fine, but bash does not get initialized.
>>
>> pw
Jerry DeLisle wrote:
> I am making the switch to 1.7. I started with a clean windows (nt4)
> environment and went through the usual run of setup-1.7 downloaded today.
>
> All appears fine, but bash does not get initialized.
>
> pwd is /usr/bin
>
> path is not set
>
> home directory is not crea
Jerry DeLisle wrote:
Dave Korn wrote:
Jerry DeLisle wrote:
Well, I am moving to this thread now.
Jerry, can I show you something you must not have realised about how
email
threading works?
Thank you for pointing this out. I usually don't use the thread view in
my mail client. I wi
Dave Korn wrote:
> This looks a _lot_ like http://support.microsoft.com/kb/327009:
The colon is not part of the URL, it was just punctuation. Here's a more
easily clickable one:
http://support.microsoft.com/kb/327009
cheers,
DaveK
--
Problem reports: http://cygwin.com/probl
I am making the switch to 1.7. I started with a clean windows (nt4) environment
and went through the usual run of setup-1.7 downloaded today.
All appears fine, but bash does not get initialized.
pwd is /usr/bin
path is not set
home directory is not created
These are all taken care of nicely
Dave Korn wrote:
Jerry DeLisle wrote:
Well, I am moving to this thread now.
Jerry, can I show you something you must not have realised about how email
threading works?
Thank you for pointing this out. I usually don't use the thread view in my mail
client. I will avoid this breakage i
Dave Korn wrote:
> Dave Korn wrote:
>> Larry Hall (Cygwin) wrote:
>>> Stephen M. Kenton wrote:
While I was there I decided to try Cygwin 1.7 and I did a new install
of everything. Shortly after it finished installing I got a strange
return from a "find" command so I scheduled a scan
Dave Korn wrote:
> Larry Hall (Cygwin) wrote:
>> Stephen M. Kenton wrote:
>
>>> While I was there I decided to try Cygwin 1.7 and I did a new install
>>> of everything. Shortly after it finished installing I got a strange
>>> return from a "find" command so I scheduled a scan disk and rebooted
>>>
Larry Hall (Cygwin) wrote:
> Stephen M. Kenton wrote:
>> While I was there I decided to try Cygwin 1.7 and I did a new install
>> of everything. Shortly after it finished installing I got a strange
>> return from a "find" command so I scheduled a scan disk and rebooted
>> so it could run. There we
Jerry DeLisle wrote:
> Well, I am moving to this thread now.
Jerry, can I show you something you must not have realised about how email
threading works?
When you hit "Reply" to an existing post, your mailer adds "In-Reply-To:"
and/or "References:" headers to your reply, so that other maile
Stephen M. Kenton wrote:
This seems to be a repeatable problem so I'm reporting it FYI
I have a dual boot Linux/Windows XP Pro box which normally runs Linux,
but the wireless card died and it turns out my replacement card does not
really work with Linux so I booted into Windows which did work
On Sun, July 5, 2009 13:49, Jerry DeLisle wrote:
> Fresh install still broken with backing down one rev on bash and using
> libreadline6.
I ran into this Friday as others have noted. The thing that caught me was
that the postinstall scripts in the installer rely on a working bash. Once
I had a bro
Christopher Faylor wrote:
On Sun, Jul 05, 2009 at 07:34:24PM -0700, Jerry DeLisle wrote:
Eric Blake wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Jerry DeLisle on 7/5/2009 1:35 PM:
Warning: There are multiple cygwin1.dlls on your path
That's probably your culprit.
I sa
On Sun, Jul 05, 2009 at 07:34:24PM -0700, Jerry DeLisle wrote:
>Eric Blake wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> According to Jerry DeLisle on 7/5/2009 1:35 PM:
>>> Warning: There are multiple cygwin1.dlls on your path
>>>
>>
>> That's probably your culprit.
>>
>I saw
Here is some more information:
bash-3.2$ ./cygcheck -s >jerrycheck
741 [main] id 85 _cygtls::handle_exceptions: Exception:
STATUS_STACK_OVERFLO
W
3209 [main] id 85 open_stackdumpfile: Dumping stack trace to
id.exe.stackdump
garbled output from 'id' command - no uid= found
1206 [main]
Dave Korn wrote:
Vincent R. wrote:
bash 3.2.49-22 OK
libreadline6 5.2.14-12 OK
libreadline7 6.0.3-1OK
Jerry DeLisle wrote:
bash 3.2.49-22
libreadline6 5.2.14-12
libreadline7 6.0.3-1
Eric Blake wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Jerry DeLisle on 7/5/2009 1:35 PM:
Warning: There are multiple cygwin1.dlls on your path
That's probably your culprit.
I saw that too and did a full search of the disk and there is only one
cygwin1.dll
I am also
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Jerry DeLisle on 7/5/2009 1:35 PM:
> Warning: There are multiple cygwin1.dlls on your path
>
That's probably your culprit.
- --
Don't work too hard, make some time for fun as well!
Eric Blake e...@byu.net
-BEGIN PGP SIG
Vincent R. wrote:
> bash 3.2.49-22 OK
> libreadline6 5.2.14-12 OK
> libreadline7 6.0.3-1OK
Jerry DeLisle wrote:
> bash 3.2.49-22
> libreadline6 5.2.14-12
> libreadline7 6.0.3-1
Err, ok.
See attached file.
Regards,
Jerry
Cygwin Configuration Diagnostics
Current System Time: Sun Jul 05 12:28:58 2009
Windows NT 4 Workstation Ver 4.0 Build 1381 Service Pack 6
Path: C:\WINNT\system32
C:\WINNT
D:\cygwin-1.7\bin
SysDir: C:\WINNT\System32
WinDir: C:\WINNT
PWD = '
On Sun, Jul 05, 2009 at 03:50:02PM -0600, Eric Blake wrote:
>-BEGIN PGP SIGNED MESSAGE-
>Hash: SHA1
>
>According to Ian Kelling on 7/5/2009 12:06 PM:
>> In the ssh package there is a bug in /usr/bin/ssh-host-config where if
>> you select a valid password spaces or punctuation that bash know
On Sun, Jul 05, 2009 at 10:49:10AM -0700, Jerry DeLisle wrote:
>Moving to this thread:
>Vincent R. wrote:
>>>I backed down on bash version which required install of libreadline6.
>>>
>>>bash still fails. This is on NT4.
>>>
>>>Maybe I need a different combination of binutils, libreadline, and
>>>b
Eric Blake wrote:
The eval is still reasonable, but with proper quoting:
if eval cygrunsrv ... -y tcpip "${cygwin_env}"
No, thats not true. It is impossible to safely eval arbitrary user input.
Your simple quote doesn't help much:
# x="ok;ls"
# eval echo "{$x}"
For more in depth information,
On 7/5/2009 7:37 PM, Christopher Faylor wrote:
I'd appreciate it if you would test this and let everyone know. You
have the power:
http://cygwin.com/snapshots/
Tried with the 2009-07-04 snapshot, and the issue is gone :-). No more
console windows are opened when launching screen and I didn't
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Ian Kelling on 7/5/2009 12:06 PM:
> In the ssh package there is a bug in /usr/bin/ssh-host-config where if
> you select a valid password spaces or punctuation that bash knows of, it
> will fail and you could possibly shoot yourself in the
On Sun, Jul 5, 2009 at 6:58 PM, Dave Korn wrote:
> It's not a full core dump, it's just a stack backtrace in human-readable
> format. If you copy and paste the addresses in the second column (Function)
> into "addr2line --exe " (and assuming you compiled
> with debug info), it'll turn them into a
> Post cygcheck output, both of you, and let's compare.
$ cygcheck -c
Cygwin Package Information
Package VersionStatus
_update-info-dir 00826-1OK
alternatives 1.3.30c-10 OK
ash 20040127-4 OK
auto
I forgot to answer two questions here.
On Sun, Jul 05, 2009 at 10:33:47AM +0100, Andy Koppe wrote:
>Now what's the right way to check for this workaround being present in
>the Cygwin DLL, so that MinTTY can skip its workaround depending on
>that? Should I parse version string from /proc/version? (
On Sun, 5 Jul 2009, Christopher Faylor wrote:
Hi,
You responded to an unrelated message and changed the subject entirely.
Please do not do that.
OK - Sorry - Klaus
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation:
This seems to be a repeatable problem so I'm reporting it FYI
I have a dual boot Linux/Windows XP Pro box which normally runs Linux,
but the wireless card died and it turns out my replacement card does not
really work with Linux so I booted into Windows which did work with card
so I could get
2009/7/5 Christopher Faylor:
>>I see the code for invoking it, but I don't fully understand it: how
>>come the helper process doesn't show up in task manager?
>
> In my testing, just starting the helper app with SW_HIDE creates a
> process which doesn't live on the toolbar. But, as the comments sa
In the ssh package there is a bug in /usr/bin/ssh-host-config where if you
select a valid password spaces or punctuation that bash knows of, it will
fail and you could possibly shoot yourself in the foot due to evaling your
password. I don't know who is responsible, or what mailing list to post
Jerry DeLisle wrote:
> Moving to this thread:
> Vincent R. wrote:
>>> I backed down on bash version which required install of libreadline6.
>>>
>>> bash still fails. This is on NT4.
>>>
>>> Maybe I need a different combination of binutils, libreadline, and bash.
>> I
>>> will play with this for a
Moving to this thread:
Vincent R. wrote:
>> I backed down on bash version which required install of libreadline6.
>>
>> bash still fails. This is on NT4.
>>
>> Maybe I need a different combination of binutils, libreadline, and bash.
> I
>> will play with this for a bit.
>>
>> Jerry
>
> I have ins
Roman Werpachowski wrote:
> On Sun, Jul 5, 2009 at 1:50 PM, Dave Korn wrote:
>> Well, what happened was that there's a bug somewhere, and while cygwin was
>> in the process of dumping the stack trace for the abort caused by your
>> assertion firing,
>
> One more question: how can I use this stack
On Sun, Jul 05, 2009 at 05:21:50PM +0100, Roman Werpachowski wrote:
>On Sun, Jul 5, 2009 at 1:50 PM, Dave Korn wrote:
>> ?Well, what happened was that there's a bug somewhere, and while cygwin was
>> in the process of dumping the stack trace for the abort caused by your
>> assertion firing,
>
>One
On Sun, Jul 05, 2009 at 06:15:51PM +0200, Sylvain Pasche wrote:
>I saw the recent thread about the unwanted console windows appearing
>with MinTTY on Win7.
>
>I just wanted to mention that I see a similar issue with screen in the
>same environment (Win7 RC 64-bit, Cygwin 1.7, screen 4.0.3-1): Each
On Sun, Jul 05, 2009 at 10:45:39AM +0200, Angelo Graziosi wrote:
>Christopher Faylor wrote:
>
>> I've made a new version of binutils
>
>Under Cygwin-1,5, trying:
>
>tar -xvf binutils-2.19.51-1-src.tar.bz2
>
>gives:
>
>-
>[...]
>binutils-2.19.5
If you need to talk about bash either change the subject or reply to the
thread which was already started about it:
http://cygwin.com/ml/cygwin/2009-07/threads.html#00105
Complaining about bash problems in reply to a binutils announcement
doesn't make any sense at all.
cgf
--
Problem reports:
On Sun, Jul 05, 2009 at 10:33:47AM +0100, Andy Koppe wrote:
>2009/7/5 Christopher Faylor:
>>As I type this I realize that I didn't really confirm that the new
>>invisible console code has the desired effect in mintty. It is
>>supposed to make some (native?) apps work better.
>
>No, its main purpos
Vincent R. wrote:
I backed down on bash version which required install of libreadline6.
bash still fails. This is on NT4.
Maybe I need a different combination of binutils, libreadline, and bash.
I
will
play with this for a bit.
Jerry
I have installed new binutils and previous bash versio
On Sun, Jul 05, 2009 at 12:32:41PM +0200, Klaus Grue wrote:
>Hi,
You responded to an unrelated message and changed the subject entirely.
Please do not do that.
cgf
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http:
> I backed down on bash version which required install of libreadline6.
>
> bash still fails. This is on NT4.
>
> Maybe I need a different combination of binutils, libreadline, and bash.
I
> will
> play with this for a bit.
>
> Jerry
I have installed new binutils and previous bash version and
On Sun, Jul 5, 2009 at 1:50 PM, Dave Korn wrote:
> Well, what happened was that there's a bug somewhere, and while cygwin was
> in the process of dumping the stack trace for the abort caused by your
> assertion firing,
One more question: how can I use this stack trace to debug genuine
errors? "gd
Hi,
I saw the recent thread about the unwanted console windows appearing
with MinTTY on Win7.
I just wanted to mention that I see a similar issue with screen in the
same environment (Win7 RC 64-bit, Cygwin 1.7, screen 4.0.3-1): Each new
screen window that is opened creates a persistent conso
Jerry DeLisle wrote:
> Maybe I need a different combination of binutils, libreadline, and bash.
Binutils can't possibly be causing shell startup failures, it's not remotely
involved(*). It's going to be between libreadline and bash.
cheers,
DaveK
--
(*) - Unless you have something
Fergus wrote:
>
> Sorry, I cannot provide cygcheck output because I cannot start a process.
Run it from cmd.exe; it's a non-cygwin (pure win32) executable, it should be
ok. It tries to launch a couple of cygwin exes; they might fail, but most of
it will work.
cheers,
DaveK
--
Prob
Dave Korn wrote:
--- snip ---
This is not a binutils bug report any longer! Try downgrading bash; there's
a problem with the new libreadline7 build, which hopefully a respin with gcc-4
and this new binutils will fix.
cheers,
DaveK
I backed down on bash version which required inst
Václav Haisman wrote:
> faiz2009 wrote, On 5.7.2009 17:26:
>> Hello,
>>
>> I try to install commoncpp2-1.7.0 under cygwin, then I proceed as follows:
>>
>> 1) . / configure (takes place without any problem).
>> 2) make. but during the compilation I receives the following error:
>>
faiz2009 wrote, On 5.7.2009 17:26:
> Hello,
>
> I try to install commoncpp2-1.7.0 under cygwin, then I proceed as follows:
>
> 1) . / configure (takes place without any problem).
> 2) make. but during the compilation I receives the following error:
> -
Hello,
I try to install commoncpp2-1.7.0 under cygwin, then I proceed as follows:
1) . / configure (takes place without any problem).
2) make. but during the compilation I receives the following error:
timer.cpp:131: error:'::clock_na
On Sun, Jul 5, 2009 at 3:28 PM, Dave Korn wrote:
> Right, well that shows you're using 1.5.25, which is known to have bugs in
> this area, and is at end-of-life and won't be fixed. It's a minor
> inconvenience, sorry, but it only affects things that happen after your
> program crashes anyway, so
On Sun, Jul 5, 2009 at 3:28 PM, Dave Korn wrote:
> Roman Werpachowski wrote:
>> On Sun, Jul 5, 2009 at 1:50 PM, Dave
>
> Please don't quote the "From:" address in your email.
Extremely sorry, won't happen again. BTW, couldn't the mailing
software automatically remove these addresses?
> Tried 1
Roman Werpachowski wrote:
> On Sun, Jul 5, 2009 at 1:50 PM, Dave
> Korn wrote:
Please don't quote the "From:" address in your email. Getting someone
spammed is no way to thank them for helping you! (See
http://cygwin.com/acronyms/#PCYMTNQREAIYR for a full explanation.)
>> Actually even more
Hi Dave,
Can anyone tell me how to invoke a program from a big-stack program ...
The problem is not spawning the new executable. The problem is ...
Thanks for the explanation.
...
955 cygthread *h = new cygthread (proc_waiter, 0, this, "proc_waiter");
...
And thanks for the very accurate fi
On Sun, Jul 5, 2009 at 1:50 PM, Dave
Korn wrote:
> Actually even more useful would be to know what Cygwin DLL version you're
> running. The problems page that CGF directed you to contains in particular
> the advice to run "cygcheck -s -v -r > cygcheck.out" and then send the
> cygcheck.out file **
Fergus wrote:
> Two packaging oddities after this update:
>
> 1) New directory \usr\i686-pc-cygwin\ containing
>
> \usr\i686-pc-cygwin\bin
> \usr\i686-pc-cygwin\bin\ar.exe.lnk
> \usr\i686-pc-cygwin\bin\as.exe.lnk
> \usr\i686-pc-cygwin\bin\ld.exe.lnk
> \usr\i686-pc-cygwin\bin\nm.exe.lnk
> \usr\i68
Pedro Izecksohn wrote:
> Will it be implemented in Cygwin someday?
If you think she can see into the future, shouldn't you be asking something
more interesting than whether cygwin will ever support rlimit, like what next
week's lottery numbers will be or how long you'll live? ;-)
Otherwise
Roman Werpachowski wrote:
> Some more details about my problem
> (http://cygwin.com/ml/cygwin/2009-07/msg00150.html)
>
> $ gcc -v
Actually even more useful would be to know what Cygwin DLL version you're
running. The problems page that CGF directed you to contains in particular
the advice to r
Dave Korn wrote:
> 207 htobe = CreateThread (&sec_none_nih, 0, is_freerange ?
> simplestub: stub,
> 208 this, 0, &id);
> 209 if (!htobe)
> 210 api_fatal ("CreateThread failed for %s - %p<%p>, %E", name,
> h, id);
This is a problem
Klaus Grue wrote:
> Hi,
>
> Can anyone tell me how to invoke a program from a big-stack program
> (i.e. a program which has a big stack). Here is a small big-stack
> program which reproduces the problem:
The problem is not spawning the new executable. The problem is that you've
set the default
Hi,
Can anyone tell me how to invoke a program from a big-stack program
(i.e. a program which has a big stack). Here is a small big-stack program
which reproduces the problem:
---
$ more example.c
#include
#include
int main(){
printf("Hello\n");
spawnlp(_P_WAIT,"ls","ls",NULL);
printf
2009/7/5 Christopher Faylor:
> I've checked in a workaround for the problem:
>
> http://cygwin.com/ml/cygwin-cvs/2009-q3/msg00010.html
>
> I checked this by removing the Windows 7 code from mintty and rebuilding
> it. With the currently released version of Cygwin 1.7.0-50 this causes
> a windows c
Christopher Faylor wrote:
I've made a new version of binutils
Under Cygwin-1,5, trying:
tar -xvf binutils-2.19.51-1-src.tar.bz2
gives:
-
[...]
binutils-2.19.51-1/opcodes/m32c-dis.c
binutils-2.19.51-1/opcodes/m32c-ibld.c
binutils-2.19.5
Two packaging oddities after this update:
1) New directory \usr\i686-pc-cygwin\ containing
\usr\i686-pc-cygwin\bin
\usr\i686-pc-cygwin\bin\ar.exe.lnk
\usr\i686-pc-cygwin\bin\as.exe.lnk
\usr\i686-pc-cygwin\bin\ld.exe.lnk
\usr\i686-pc-cygwin\bin\nm.exe.lnk
\usr\i686-pc-cygwin\bin\ranlib.exe.lnk
\u
70 matches
Mail list logo
