From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11412 invoked from network); 13 Oct 2000 22:27:01 -0000 Received: from sunsite.auc.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 13 Oct 2000 22:27:01 -0000 Received: (qmail 16228 invoked by alias); 13 Oct 2000 22:26:24 -0000 Mailing-List: contact zsh-workers-help@sunsite.auc.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 12999 Received: (qmail 16221 invoked from network); 13 Oct 2000 22:26:22 -0000 From: "Bart Schaefer" Message-Id: <1001013222617.ZM5690@candle.brasslantern.com> Date: Fri, 13 Oct 2000 22:26:17 +0000 In-Reply-To: <39E62288.BE76D77F@lycos-inc.com> Comments: In reply to Gray Watson "zsh 3.1.9 problem debugging linux threads" (Oct 12, 4:43pm) References: <39E62288.BE76D77F@lycos-inc.com> X-Mailer: Z-Mail (5.0.0 30July97) To: zsh-workers@sunsite.auc.dk Subject: Re: zsh 3.1.9 problem debugging linux threads MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii For the record: On Oct 12, 4:43pm, Gray Watson wrote: } } I cannot debug threaded programs under Linux RH6.2 with gdb: } } Program received signal SIGTTOU, Stopped (tty output). } 0x4011ab14 in __libc_write () from /lib/libc.so.6 } } Gdb suspends itself without any keystrokes from mine. If I log in under } another shell, I have no problems. Wierd huh? I've been trading some private mail with Gray, and this problem turns out to be a gdb issue rather than a zsh issue. The reason that zsh was the only shell exhibiting the behavior had to do with "stty tostop" combined with some confusion over "ttyctl -f". Gdb exhibits the same behavior in bash if "stty tostop" is in effect. I've suggested that Gray report this to the gdb bug list. -- Bart Schaefer Brass Lantern Enterprises http://www.well.com/user/barts http://www.brasslantern.com Zsh: http://www.zsh.org | PHPerl Project: http://phperl.sourceforge.net