On Thu, 30 Dec 2004 at 18:23:39 PM -0500, Christopher Faylor wrote:
>
> You missed step 5, apparently.
Well, actually, no, I didn't miss it, but step 5 did not appear to
yield any additional information. If I continue several times, I get:
> (gdb) run
> Starting program: /c/scratch/usr/bin/mount
On Thu, Dec 30, 2004 at 03:15:22PM -0800, David Hinds wrote:
>On Thu, 2 Dec 2004 at 09:36:21 AM -0500, Christopher Faylor wrote:
>
>> Could you try running this under gdb to see if you get more of a clue
>> about where cygwin is dying? The last entry in the snapshot is not
>> necessarily indicativ
On Thu, 2 Dec 2004 at 09:36:21 AM -0500, Christopher Faylor wrote:
> Could you try running this under gdb to see if you get more of a clue
> about where cygwin is dying? The last entry in the snapshot is not
> necessarily indicative of this.
[ recap: my problem is that on a dual Xeon workstation
On Wed, Dec 01, 2004 at 10:44:34AM -0800, David Hinds wrote:
>I've attached "strace" output from running "ls". The output is
>slightly different from previous attempts, because I'd been able to
>run the postinstall scripts to populate /etc/passwd and /etc/group;
>but the failure mode appears uncha
On Wed, Dec 01, 2004, Gerrit P. Haase wrote:
> have you already tried to run the crashing application with
> dependency walker? http://www.dependencywalker.com/
No, I was not familiar with this tool. I've attached the profile
output for an invocation of "readlink.exe".
-- Dave
--
Christopher Faylor schrieb:
On Wed, Dec 01, 2004 at 07:58:25PM +0100, Reini Urban wrote:
And you really think using a UNC path $HOME is a good idea? And you
really think you must send us this strace just for telling us that
cygwin didn't like your UNC path $HOME?
Reini, I asked for the strace. I
Hi,
have you already tried to run the crashing application with
dependency walker? http://www.dependencywalker.com/
Gerrit
--
=^..^=
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/do
On Wed, Dec 01, 2004 at 07:58:25PM +0100, Reini Urban wrote:
>And you really think using a UNC path $HOME is a good idea? And you
>really think you must send us this strace just for telling us that
>cygwin didn't like your UNC path $HOME?
Reini, I asked for the strace. I don't think that the UNC
David Hinds schrieb:
Drat... Windows Update decided to install a "critical security fix"
last night, and today, Cygwin appears to be 100% dead in the water as
opposed to yesterday's 90%. The security fix is supposed to be in
Internet Explorer so it might just be a coincidence.
I've attached "strac
On Wed, Dec 01, 2004 at 10:44:34AM -0800, David Hinds wrote:
> Drat... Windows Update decided to install a "critical security fix"
> last night, and today, Cygwin appears to be 100% dead in the water as
> opposed to yesterday's 90%. The security fix is supposed to be in
> Internet Explorer so it m
Drat... Windows Update decided to install a "critical security fix"
last night, and today, Cygwin appears to be 100% dead in the water as
opposed to yesterday's 90%. The security fix is supposed to be in
Internet Explorer so it might just be a coincidence.
I've attached "strace" output from runni
On Tue, 30 Nov, 2004 at 05:50:29PM -, Dave Korn wrote:
> Well, I suppose so, but subtle and borderline hardware failures can have
> ever such bizarre, transient, and unpredictable consequences (cf. memory
> timing issues and Sig11 failures at times of heavy stress
Sure... but I don't think ru
On Mon, Nov 29, 2004 at 10:32:09PM -0500, Christopher Faylor wrote:
> Cygwin initialization code isn't particularly hard to debug. You just
> set breakpoints and debug it like any other part of cygwin. It's
> actually easier to debug than most other pieces because there aren't
> multiple threads
On Sun, Nov 28, 2004 at 11:14:51PM -0800, David Hinds wrote:
>A couple days ago, I tried to update a quite old cygwin installation
>on a Windows XP SP2 box to the latest (1.5.12-1). After the update,
>all Cygwin programs exit immediately and silently. I've tried
>scrubbing the Windows registry of
> -Original Message-
> From: cygwin-owner On Behalf Of David Hinds
> Sent: 30 November 2004 17:08
> On Tue, 30 Nov, 2004 at 01:38:39PM -, Dave Korn wrote:
> >
> > I reckon you most likely have faulty hardware in there somewhere
>
> Err, it seems exceedingly unlikely that this heavily
On Tue, 30 Nov, 2004 at 01:38:39PM -, Dave Korn wrote:
>
> I reckon you most likely have faulty hardware in there somewhere
Err, it seems exceedingly unlikely that this heavily used system which
has worked perfectly for several years, would have faulty hardware
that specifically dislikes cygwi
On Tue, Nov 30, 2004 at 01:50:03PM -, Matt Ross wrote:
>What was the last version of Cygwin before signal handling was enabled?
? Cygwin has always had signal handling and that particular message
has existed unchanged since 02-Aug-00.
--
Unsubscribe info: http://cygwin.com/ml/#unsubscri
On Tue, Nov 30, 2004 at 02:54:54PM -, Dave Korn wrote:
>> -Original Message-
>> From: cygwin-owner On Behalf Of Fergus Daly
>> Sent: 30 November 2004 14:19
>
>> > Probably a false alarm.
>> > Is '.' in your $PATH?
>> No.
>> Fergus
>
>
>Nevermindallthatnow, why have you suddenly changed
On Tue, Nov 30, 2004 at 01:14:08PM -, [EMAIL PROTECTED] wrote:
>With so many planet-sized intellects working away at this I am a bit nervous
>about making yet another contribution of the style "how's this for weird?".
I don't see what's particularly weird about this or what this email has
to d
> -Original Message-
> From: cygwin-owner On Behalf Of Fergus Daly
> Sent: 30 November 2004 14:19
> > Probably a false alarm.
> > Is '.' in your $PATH?
> No.
> Fergus
Nevermindallthatnow, why have you suddenly changed your surname? :-O
Nonetheless I can confirm that it's a false
> Probably a false alarm.
> Is '.' in your $PATH?
No.
Fergus
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
I too have been experiencing this whole problem on a hp DL360G3 server that
up until recently was happily running Cygwin and SSH. When I did a Cygwin
update about a fortnight ago I didn't notice anything was wrong until I
rebooted the server. Then SSH would not start. As it turns out, nearly all
th
> -Original Message-
> From: cygwin-owner On Behalf Of David Hinds
> Sent: 30 November 2004 01:14
> On Mon, Nov 29, 2004 at 06:22:35PM -0500, Larry Hall wrote:
> >
> > Yeah, I understand. This is certainly not your everyday
> issue, as you've
> > noticed. I suppose it's worthwhile to l
> -Original Message-
> From: cygwin-owner On Behalf Of [EMAIL PROTECTED]
> Sent: 30 November 2004 13:14
> On my system I have so contrived things that I have exactly
> one (yes promise
> and hope to die horribly) exactly one cygwin1.dll and there
> ain't nothing
> else at all, anywhere.
With so many planet-sized intellects working away at this I am a bit nervous
about making yet another contribution of the style "how's this for weird?".
But
On my system I have so contrived things that I have exactly one (yes promise
and hope to die horribly) exactly one cygwin1.dll and there ain'
>If that doesn't work, entirely wipe out c:\local\cygwin, run regedit,
and remove the "HKLM/Cygnus Solutions" and the HKCU/Cygnus Solutions
keys entirely. >Then reboot and try reinstalling just a minimal
installation.
If you run cygcheck to check that your system is clear of cygwin note
that it a
On Mon, Nov 29, 2004 at 08:25:21PM -0500, Igor Pechtchanski wrote:
>This suggests some sort of a problem with the Cygwin DLL initialization
>code -- something that's very hard to debug. Try looking at the CVS
>history for the Cygwin initialization code between the 1.5.5 and 1.5.6
>releases.
Cygwi
On Mon, 29 Nov 2004, David Hinds wrote:
> On Mon, Nov 29, 2004 at 06:22:35PM -0500, Larry Hall wrote:
> >
> > Yeah, I understand. This is certainly not your everyday issue, as you've
> > noticed. I suppose it's worthwhile to look at the settings for the Windows
> > firewall to see if it's being
On Mon, Nov 29, 2004 at 06:22:35PM -0500, Larry Hall wrote:
>
> Yeah, I understand. This is certainly not your everyday issue, as you've
> noticed. I suppose it's worthwhile to look at the settings for the Windows
> firewall to see if it's being overly restrictive or limiting in some way.
> Sorr
At 06:17 PM 11/29/2004, you wrote:
>On Mon, Nov 29, 2004 at 05:22:28PM -0500, Larry Hall wrote:
>> >
>> >File permissions appear ok as far as I can tell. The 'strace' output
>> >seems consistent with no permission problems; I'm able to execute all
>> >commands, cygwin1.dll is found, and things run
On Mon, Nov 29, 2004 at 05:22:28PM -0500, Larry Hall wrote:
> >
> >File permissions appear ok as far as I can tell. The 'strace' output
> >seems consistent with no permission problems; I'm able to execute all
> >commands, cygwin1.dll is found, and things run for a short while
> >before dying.
>
>
At 04:52 PM 11/29/2004, you wrote:
>On Mon, Nov 29, 2004 at 03:18:05PM -0500, Larry Hall wrote:
>> At 02:59 PM 11/29/2004, you wrote:
>> >The postinstall scripts are all cygwin shell scripts and thus require
>> >a functional 'sh' to do anything. And, as with all other cygwin
>> >programs, 'sh' jus
On Mon, Nov 29, 2004 at 15:34:00 PM -0500, Christopher Faylor wrote:
> Sounds like you haven't read http://cygwin.com/problems.html, in that
> case.
I read it quickly for exactly this reason, and then misinterpreted
"just attach it as a straight text file". Just a moment of idiocy.
> cygcheck a
On Mon, Nov 29, 2004 at 03:18:05PM -0500, Larry Hall wrote:
> At 02:59 PM 11/29/2004, you wrote:
> >The postinstall scripts are all cygwin shell scripts and thus require
> >a functional 'sh' to do anything. And, as with all other cygwin
> >programs, 'sh' just exits without doing anything.
>
>
On Mon, Nov 29, 2004 at 11:59:47AM -0800, David Hinds wrote:
>On Mon, Nov 29, 2004 at 01:59:07PM -0500, Larry Hall wrote:
>>
>> We prefer *attached* output.
>
>Sorry about that; some lists discourage attachments.
Sounds like you haven't read http://cygwin.com/problems.html, in that case.
>> Any
At 02:59 PM 11/29/2004, you wrote:
>The postinstall scripts are all cygwin shell scripts and thus require
>a functional 'sh' to do anything. And, as with all other cygwin
>programs, 'sh' just exits without doing anything.
Yep, so I'd recommend starting there. Check the Windows properties here
On Mon, Nov 29, 2004 at 01:59:07PM -0500, Larry Hall wrote:
>
> We prefer *attached* output.
Sorry about that; some lists discourage attachments.
> Anyway, I agree with Chris's comments, even
> though it's not obvious that this is the problem. Look for duplicate
> cygwin1.dlls, remove them,
added the packages I wanted...not
that I didn't want the default stuff (;.)
The new install was uneventful.
From: Larry Hall
Reply-To: Cygwin List
To: David Hinds, Cygwin List
Subject: Re: A vexing installation problem
Date: Mon, 29 Nov 2004 13:59:07 -0500
At 01:44 PM 11/29/2004, you wrote:
&g
At 01:44 PM 11/29/2004, you wrote:
>On Mon, Nov 29, 2004 at 11:57:35AM -0500, Larry Hall wrote:
>> At 02:14 AM 11/29/2004, you wrote:
>> >A couple days ago, I tried to update a quite old cygwin installation
>> >on a Windows XP SP2 box to the latest (1.5.12-1). After the update,
>> >all Cygwin prog
On Mon, Nov 29, 2004 at 10:44:42AM -0800, David Hinds wrote:
>On Mon, Nov 29, 2004 at 11:57:35AM -0500, Larry Hall wrote:
>> At 02:14 AM 11/29/2004, you wrote:
>> >A couple days ago, I tried to update a quite old cygwin installation
>> >on a Windows XP SP2 box to the latest (1.5.12-1). After the u
On Mon, Nov 29, 2004 at 11:57:35AM -0500, Larry Hall wrote:
> At 02:14 AM 11/29/2004, you wrote:
> >A couple days ago, I tried to update a quite old cygwin installation
> >on a Windows XP SP2 box to the latest (1.5.12-1). After the update,
> >all Cygwin programs exit immediately and silently. I'v
At 02:14 AM 11/29/2004, you wrote:
>A couple days ago, I tried to update a quite old cygwin installation
>on a Windows XP SP2 box to the latest (1.5.12-1). After the update,
>all Cygwin programs exit immediately and silently. I've tried
>scrubbing the Windows registry of anything with a "Cyg" in
A couple days ago, I tried to update a quite old cygwin installation
on a Windows XP SP2 box to the latest (1.5.12-1). After the update,
all Cygwin programs exit immediately and silently. I've tried
scrubbing the Windows registry of anything with a "Cyg" in it,
deleting the Cygwin tree, and reins
43 matches
Mail list logo
