On 6/6/2010 8:32 PM, Reini Urban wrote:

=========

262: my ($self,$cmd,$in,$out,$err) = @_;
263: carp qq{Debug (syswait): Running "$cmd"\n} if($Verbose);
265: my $status;
266: my $child_pid;
267: if ($child_pid = fork) {

You can try to add a small sleep here after line 267, the fork.
         sleep(0.2);

268: $status = waitpid($child_pid, 0);
######### Forked, but do not know how to create a new TTY. #########

Hello;

I added the sleep above, made no difference: (also tried with sleep(.5), same, the error still there:

====================================

  entering L2hos::Unix::syswait
     262:         my ($self,$cmd,$in,$out,$err) = @_;
     263:         carp qq{Debug (syswait): Running "$cmd"\n} if($Verbose);
     265:         my $status;
     266:         my $child_pid;
     267:         if ($child_pid = fork) {
     268:           sleep(0.2);
     269:           $status = waitpid($child_pid, 0);
######### Forked, but do not know how to create a new TTY. #########
  Since two debuggers fight for the same TTY, input is severely entangled.

  I know how to switch the output to a different window in xterms, OS/2
consoles, and Mac OS X Terminal.app only. For a manual switch, put the name
  of the created TTY in $DB::fork_TTY, or define a function
  DB::get_fork_TTY() returning this.

  On UNIX-like systems one can get the name of a TTY for the given window
  by typing tty, and disconnect the shell from TTY by sleep 1000000.

     275:           unless(exec($cmd)) {
0 [main] perl 4796 C:\cygwin\bin\perl.exe: *** fatal error - Internal error: TP_NUM_W_BUFS too small. 270: carp "Debug (syswait): Finished child process: #$child_pid\n"
     271:             if($Verbose);
     272:           $child_pid = 0;
     273:           return($?);
    exited L2hos::Unix::syswait

==================

--Nasser

--
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 via email to