Re: WTF is going on? pipe breakage, patch(1) breakage??

2002-08-17 Thread Tim Robbins
FWIW, the pipe breakage seems to have been caused by /bin/sh freeing the job table (jobs.c lines 744-746) then later using a value in the freed region as an argument to setpgid() and tcsetpgrp() (jobs.c lines 753-760) when the job had more than one process in it (a pipeline). phkmalloc was

Re: WTF is going on? pipe breakage, patch(1) breakage??

2002-08-13 Thread Tim Robbins
I'm definitely seeing problems with pipes, and major problems with the tty process group/session/job control/etc. code. I've had commands like: cvs diff -Nu | less terminate after showing one screenful with cvs recieving SIGPIPE; the same command sometimes causes my login shell to get

Re: WTF is going on? pipe breakage, patch(1) breakage??

2002-08-13 Thread Alexander Kabaev
This can be related: occasionally top terminates after displaying the process list only once. Unfortunately, this is hard to reproduce and when run again top just start working properly. -- Alexander Kabaev To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the