Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com X-Originating-IP: [66.206.205.2] X-Originating-Email: [vxj45 AT hotmail DOT com] From: "Vishal Jain" To: cygwin AT cygwin DOT com Subject: Re: Building 1.3.22 from src (WAS: Re: (1.3.22) mount: strange 15 second delay) Date: Fri, 18 Apr 2003 09:34:00 -0700 Mime-Version: 1.0 Content-Type: text/plain; format=flowed Message-ID: X-OriginalArrivalTime: 18 Apr 2003 16:34:00.0874 (UTC) FILETIME=[5119A8A0:01C305C8] Note-from-DJ: This may be spam You need to put mingw in winsup/ and then compile. Check out mails around 11th April in the mailing list Vishal Rolf Campbell wrote: >Christopher Faylor wrote: > >>On Thu, Apr 17, 2003 at 07:30:00PM -0400, Rolf Campbell wrote: >> >>>I straced it (and the problem went away) so, I straced 'bash -c mount' >>>and the problem came back. The relavent portion of the strace is: >>> >>>118 4305 [main] mount 2388 normalize_posix_path: src /dev/pipew >>> 87 4392 [main] mount 2388 normalize_posix_path: /dev/pipew = >>>normalize_posix_path (/dev/pipew) >>>113 4505 [main] mount 2388 mount_info::conv_to_win32_path: >>>conv_to_win32_path (/dev/pipew) >>>113 4618 [main] mount 2388 mount_info::conv_to_win32_path: src_path >>>/dev/pipew, dst \dev\pipew, flags 0x2, rc 0 >>> 90 4708 [main] mount 2388 fhandler_base::fstat: here >>>100 4808 [main] mount 2388 fstat64: 0 = fstat (1, 0x22E8E0) >>>11282054 11286862 [main] mount 2388 writev: writev (1, 0x22FDE0, 1) >>>257 11287119 [main] mount 2388 fhandler_base::write: binary write >>>125 11287244 [main] mount 2388 fhandler_base::write: 399 = write >>>(0xA0403D8, 399) >>> 90 11287334 [main] mount 2388 writev: 399 = write (1, 0x22FDE0, 1), >>>errno 0 >>> 91 11287425 [main] mount 2388 do_exit: do_exit (0) >>> >>>The 'writev' takes 11.2 seconds to complete. Could somebody give me a >>>hint what is going on here? >> >>The timestamp isn't time to complete. It's time since last timestamp. >>So something between fstat and writev took 11282054 microseconds. > >Ok, I recompiled the mount.exe program with -ggdb. The delay was in on >line 382. The last call to getmntent (the one that returns NULL) is the >one that takes > 10 seconds. > >Was hoping that this would spark a thought in someone. I'll start trying >to get a debug cygwin load building to test further. I tried to build cygwin. Ran into problems: In file included from /usr/include/w32api/windows.h:98, from ../../../../cygwin-1.3.22-1/winsup/utils/cygcheck.cc:17: /usr/include/w32api/winsock2.h:95:2: warning: #warning "fd_set and associated macros have been defined in sys/types. This may cause runtime problems with W32 sockets" In file included from /usr/include/w32api/windows.h:98, from ../../../../cygwin-1.3.22-1/winsup/utils/cygcheck.cc:17: /usr/include/w32api/winsock2.h:101: redefinition of `struct timeval' /usr/src/cygwin-1.3.22-1/newlib/libc/include/sys/time.h:16: previous definition of `struct timeval' In file included from ../../../../cygwin-1.3.22-1/winsup/utils/cygcheck.cc:19: /usr/src/cygwin-1.3.22-1/winsup/cygwin/include/sys/cygwin.h:229: '__uid16_t' is used as a type, but is not defined as a type. /usr/src/cygwin-1.3.22-1/winsup/cygwin/include/sys/cygwin.h:230: '__gid16_t' is used as a type, but is not defined as a type. /usr/src/cygwin-1.3.22-1/winsup/cygwin/include/sys/cygwin.h:248: '__uid32_t' is used as a type, but is not defined as a type. /usr/src/cygwin-1.3.22-1/winsup/cygwin/include/sys/cygwin.h:249: '__gid32_t' is used as a type, but is not defined as a type. _________________________________________________________________ STOP MORE SPAM with the new MSN 8 and get 2 months FREE* http://join.msn.com/?page=features/junkmail -- 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/