This is the mail archive of the cygwin mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Please try a snapshot - final push for 1.5.19

On Wed, 21 Dec 2005, Christopher Faylor wrote:

> Only four more testing days remain if we want to get a cygwin 1.5.19
> release out there by Christmas.  Please try a snapshot and report
> success/failure to this thread.
> When reporting a problem please report the exact steps that you've taken
> and *please* narrow down the failure to the absolute minimum scenario
> needed to duplicate it.
> So, please try the 2005-Dec-21 snapshot: .

I've been having problems with "fork: resource unavailable" on my machine
with the 10/03 snapshot.  The problem is only reproducible after Cygwin
has been running for a while, under a heavy load.  I'll try to see if it
appears under the 12/20 snapshot, but there's no guarantee I'll be able to
reproduce it in time for the release.  I know this isn't much of a bug
report, but this is just a heads-up.

I'm at a loss on how to proceed.  Would an strace captured under the 10/03
snapshot be helpful at all?  If not, would it at least be possible to add
the relevant debugging information to the fork() code, so that when I do
reproduce this (and I have a feeling that in a few days, I'll be able to),
I can get meaningful information from the strace even with the outdated
snapshot?  Unfortunately, the whole nature of the problem setting
precludes using the latest snapshot...  I also have a feeling that this
would be next to impossible to reproduce on other machines...

FWIW, here's the (IMO) relevant bit of the strace, captured under the
10/03 snapshot.  I don't know how normal it is for a newly-created process
to have the PID_EXITED bit set:

   22   76572 [main] bash 12000 fork: entering
   20   76592 [main] bash 12000 sig_send: sendsig 0x734, pid 12000, signal -40, its_me 1
   22   76614 [main] bash 12000 sig_send: wakeup 0x6E4
   27   76641 [main] bash 12000 sig_send: Waiting for pack.wakeup 0x6E4
   26   76667 [main] bash 12000 sig_send: returning 0x0 from sending signal -40
  255   76922 [main] bash 12000 stack_base: bottom 0x230000, top 0x22E72C, stack 0x22E72C, size 6356, reserve 6356
   21   76943 [main] bash 12000 frok::parent: CreateProcess (C:\cygwin\bin\bash.exe, C:\cygwin\bin\bash.exe, 0, 0, 1, 0x20, 0, 0, 0x22E730, 0x22E7A0)
 1180   78123 [sig] bash 12000 wait_sig: signalled 0x6E4

(the part below is repeated 20 times)
   37   89289 [main] bash 12000 open_shared: name (null), n 11608, shared 0x1470000 (wanted 0x0), h 0x6D4
   22   89311 [main] bash 12000 pinfo::init: looping because pid 11608, procinfo->pid 11608, procinfo->dwProcessid 6644 has PID_EXITED set
(the part above is repeated 20 times)

   38   89349 [main] bash 12000 frok::parent: pinfo failed
   28   89377 [main] bash 12000 frok::parent: returning -1
   18   89395 [main] bash 12000 fork: fork failed - child pid 11608, errno 11
   19   89414 [main] bash 12000 __set_errno: int fork():602 val 11
   19   89433 [main] bash 12000 fork: -1 = fork()

Any pointers/advice would be appreciated.
      |\      _,,,---,,_
ZZZzz /,`.-'`'    -.  ;-;;,_
     |,4-  ) )-,_. ,\ (  `'-'		Igor Pechtchanski, Ph.D.
    '---''(_/--'  `-'\_) fL	a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

"Las! je suis sot... -Mais non, tu ne l'es pas, puisque tu t'en rends compte."
"But no -- you are no fool; you call yourself a fool, there's proof enough in
that!" -- Rostand, "Cyrano de Bergerac"

Unsubscribe info:
Problem reports:

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]