On Feb 15 10:07, Chuck wrote:
> [...]
> 135 198219 [main] ls 3172 seterrno_from_win_error:
> /ext/build/netrel/src/cygwin-1.5.24-2/winsup/cygwin/fhandler.cc:687 windows
> error 3
>78 198297 [main] ls 3172 geterrno_from_win_error: windows error 3 ==
> errno 2
>64 198361 [main] ls 317
This latest strace of my problem contains a few windows errors. Can
anyone tell what the root problem is? Strace.out is attached. Thanks.
**
Program name: C:\cygwin\bin\ls.exe (pid 3172, ppid 1)
App version: 1005.23, api: 0.156
DLL version: 1005.24,
Ken Shaffer wrote:
>>> Any other ideas? Anyone?
>
> Perhaps your filenames have special characters in them which do funny
> things to your terminal.
>
> Try "ls -ad .* * | cat -v".
Doesn't show anything unusual.
>
> Are the serial numbers on the physical drives unique?
There's only one physic
Frodak Baksik wrote:
> On 2/14/07, Chuck <[EMAIL PROTECTED]> wrote:
>>
>
> What is actually in your home folder?
> Also how did you create this trace? It appears to be truncated. Or
> at least ls never got past the point where it reads the contents of
> the directory. You'll notice that it nev
Any other ideas? Anyone?
Perhaps your filenames have special characters in them which do funny
things to your terminal.
Try "ls -ad .* * | cat -v".
Are the serial numbers on the physical drives unique?
From a DOS window, enter "dir":
Volume in drive C has no label.
Volume Seri
On 2/14/07, Chuck <[EMAIL PROTECTED]> wrote:
Chuck wrote:
> Shankar Unni wrote:
>
>> Obviously something odd about that share. Chuck: can you tell if there's
>> something unusual about the server that exports that share (as opposed
>> to the other drives you have, like K: and G:)?
>>
>>
>
> Nothi
Chuck wrote:
> Shankar Unni wrote:
>
>> Obviously something odd about that share. Chuck: can you tell if there's
>> something unusual about the server that exports that share (as opposed
>> to the other drives you have, like K: and G:)?
>>
>>
>
> Nothing unusual about that share. I can even repro
Shankar Unni wrote:
>
> Obviously something odd about that share. Chuck: can you tell if there's
> something unusual about the server that exports that share (as opposed
> to the other drives you have, like K: and G:)?
>
>
Nothing unusual about that share. I can even reproduce the problem on a
Chuck wrote:
Attached files are output from "cygcheck -s -v -r > cygcheck.out", and
and an strace of a failed execution of "ls /cygdrive". By failed I mean
that the command produced no output.
That's funny.
The readdir() is cranking along, and reads c, g, h and k. Each of these
consists of t
9 matches
Mail list logo
