Zsh Mailing List Archive Messages sorted by: Reverse Date, Date, Thread, Author

Re: Re: zsh 3.1.9 problem debugging linux threads

X-seq: zsh-workers 12992
From: Gray Watson <gray.reply@xxxxxxx>
To: zsh-workers@xxxxxxxxxxxxxx
Subject: Re: Re: zsh 3.1.9 problem debugging linux threads
Date: Thu, 12 Oct 2000 19:07:25 -0400 (EDT)
In-reply-to: id: "<m13jpzg-000QqbC@xxxxxxxxxxxxxxx>", date "Thu, 12 Oct 2000 17:34:28 -0400 (EDT)"
Mailing-list: contact zsh-workers-help@xxxxxxxxxxxxxx; run by ezmlm
Reply-to: gray@xxxxxxx

> > 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@xxxxxxx

Follow-Ups:
- Re: zsh 3.1.9 problem debugging linux threads
  - From: Bart Schaefer

References:
- Re: zsh 3.1.9 problem debugging linux threads
  - From: Gray Watson

Messages sorted by: Reverse Date, Date, Thread, Author