From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7265 invoked from network); 12 Oct 2000 23:08:04 -0000 Received: from sunsite.auc.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 12 Oct 2000 23:08:04 -0000 Received: (qmail 24943 invoked by alias); 12 Oct 2000 23:07:27 -0000 Mailing-List: contact zsh-workers-help@sunsite.auc.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 12992 Received: (qmail 24926 invoked from network); 12 Oct 2000 23:07:27 -0000 Message-Id: Date: Thu, 12 Oct 2000 19:07:25 -0400 (EDT) To: zsh-workers@sunsite.auc.dk In-reply-to: id: "", date "Thu, 12 Oct 2000 17:34:28 -0400 (EDT)" Subject: Re: Re: zsh 3.1.9 problem debugging linux threads From: Gray Watson Reply-to: gray@256.com > > I cannot debug threaded programs under Linux RH6.2 with gdb: > ... > > This is a problem only when the monitor option is enabled which > controls the signal SIGTTOU. I'm not sure why but it looks like this > signal is generated from inside of a linux threaded application. Scratch that. It is SIGCHLD. Looks like the pthread clone delivers a SIGCHLD and zsh thinks that gdb is being suspended for some reason. Question: What file/line of the zsh code actually writes out this line? It seems to not be in any of the signal handlers nor waitpid/job/jobs functions. This would be helpful in finding out how the child signal is being processed. zsh: 2161 suspended (tty output) gdb intel_redhat_6_2/cmd Thanks much, --- gray.reply@256.com