public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: pen <pen_1232000@yahoo.com>
To: cygwin@cygwin.com
Subject: commands spends time in cygheap_user
Date: Fri, 17 Jul 2015 06:26:00 -0000	[thread overview]
Message-ID: <1437114390582-119766.post@n5.nabble.com> (raw)

simple commands like ls taking long time in "cygheap_user". May i have some
pointers to what to check?
Already checked path/cygcheck/nsswitch but all looks fine. here is sample
strace.

      14    4973 [main] ls 9308 App version:  1007.32, api: 0.274
   14    4987 [main] ls 9308 DLL version:  2001.0, api: 0.287
   19    5006 [main] ls 9308 DLL build:    2015-07-14 21:26
   21    5027 [main] ls 9308 dtable::extend: size 32, fds 0x612EFB50
  222    5249 [main] ls 9308 transport_layer_pipes::connect: Try to connect
to named pipe: \\.\pipe\cygwin-685dc4bb75d52efd-lpc
   39    5288 [main] ls 9308 transport_layer_pipes::connect: Error opening
the pipe (2)
   29    5317 [main] ls 9308 client_request::make_request: cygserver
un-available
--- Process 9308 loaded C:\Windows\SysWOW64\advapi32.dll at 756D0000
--- Process 9308 loaded C:\Windows\SysWOW64\msvcrt.dll at 75490000
--- Process 9308 loaded C:\Windows\SysWOW64\sechost.dll at 77290000
--- Process 9308 loaded C:\Windows\SysWOW64\rpcrt4.dll at 75870000
--- Process 9308 loaded C:\Windows\SysWOW64\sspicli.dll at 75300000
--- Process 9308 loaded C:\Windows\SysWOW64\cryptbase.dll at 752F0000
--- Process 9308 thread 5864 created
 5919   11236 [sig] ls 9308 wait_sig: entering ReadFile loop, my_readsig
0x8C, my_sendsig 0x90
--- Process 9308 thread 7472 created
2441548 2452784 [main] ls 9308 cygheap_user::ontherange: what 2, pw
0x612EFCE8      <<<
  135 2452919 [main] ls 9308 cygheap_user::ontherange: HOME is already in
the environment /home/pen
  308 2453227 [main] ls 9308 build_argv: argv[0] = 'ls'





--
View this message in context: http://cygwin.1069669.n5.nabble.com/commands-spends-time-in-cygheap-user-tp119766.html
Sent from the Cygwin list mailing list archive at Nabble.com.

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

             reply	other threads:[~2015-07-17  6:26 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-17  6:26 pen [this message]
2015-08-07  8:48 ` mku
2015-08-07  9:06   ` Corinna Vinschen
2015-08-07 19:51     ` mku
2015-08-10  8:40       ` Corinna Vinschen
2015-08-10 12:00         ` mku
2015-08-10 16:01           ` Corinna Vinschen
2015-08-12 11:59             ` mku
2015-08-12 14:47               ` Corinna Vinschen
2015-08-14 13:49                 ` mku
2015-08-14 15:48                   ` Corinna Vinschen
2015-08-14 20:20                     ` Corinna Vinschen
2015-08-15 11:54                       ` Corinna Vinschen
2015-08-16 12:50                         ` mku
2015-08-17  8:07                           ` Corinna Vinschen
2015-08-17  8:13                             ` Corinna Vinschen
2015-08-17 10:10                               ` mku
2015-08-17 20:55                               ` Corinna Vinschen
2015-08-17 21:04                                 ` Corinna Vinschen
2015-08-18  8:17                                   ` mku
2015-08-18  8:30                                     ` Corinna Vinschen
2015-08-14 13:49             ` Corinna Vinschen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1437114390582-119766.post@n5.nabble.com \
    --to=pen_1232000@yahoo.com \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).