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, 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, 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
--
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
&
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 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 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
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.
>
>
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 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,
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
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
15 matches
Mail list logo
