zsh-workers
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-workers@zsh.org
Subject: Re: Bug related to stdin/always/jobcontrol
Date: Thu, 22 Sep 2016 18:18:47 -0700	[thread overview]
Message-ID: <160922181847.ZM22524@torch.brasslantern.com> (raw)
In-Reply-To: <160922093838.ZM7266@torch.brasslantern.com>

On Sep 22,  9:38am, Bart Schaefer wrote:
} Subject: Re: Bug related to stdin/always/jobcontrol
}
} On Sep 22, 11:59am, Daniel Shahaf wrote:
} }
} } % f() { $EDITOR } 
} } % f
} } <press ^Z in the editor>
} } zsh: suspended  f
} } % fg
} } [1]  + continued  f
} } zsh: suspended (tty output)  f
} 
} Worse that that, signals go to the parent shell:
} 
} torch% kill -9 %1
} Vim: Caught deadly signal HUP
} Vim: Finished.
} zsh: killed     Src/zsh -f

The signal is being sent from here (signals.c):

755                 if (killpg(jobtab[jn->other].gleader, sig) == -1 && errno != ESRCH)

The problem is that jobtab[jn->other].gleader is 0, so killpg kills the
current process.

Obviously the group leader should never be zero, but I haven't figured
out how to track down where it's [not] being set.  Probably this is
related to the shell function not properly attaching to the tty when
foregrounded.

However, in attempting to figure it out, I found some sixteen-year-old
code that is clearly wrong:

diff --git a/Src/exec.c b/Src/exec.c
index d924148..bf97b5c 100644
--- a/Src/exec.c
+++ b/Src/exec.c
@@ -1702,7 +1702,7 @@ execpline(Estate state, wordcode slcode, int how, int last1)
 			    jobtab[list_pipe_job].other = newjob;
 			    jobtab[list_pipe_job].stat |= STAT_SUPERJOB;
 			    jn->stat |= STAT_SUBJOB | STAT_NOPRINT;
-			    jn->other = pid;
+			    jn->other = list_pipe_job;
 			    jn->gleader = jobtab[list_pipe_job].gleader;
 			}
 			if ((list_pipe || last1) && hasprocs(list_pipe_job))

jn->other is a job table index, not a process ID.  However, (a) I don't
know if list_pip_job is the right value (although a few lines earlier
list_pipe_pid = pid is assigned, so it would seem to makes sense) and
(b) that this has never caused a wild pointer dereference in all this
time seems to indicate that this code is never actually reached.

I don't have any more time to look at this now; hoping this information
is helpful to PWS if he has a chance to look when he wakes up on Friday.


  reply	other threads:[~2016-09-23  1:18 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-02 18:39 Christian Neukirchen
2016-09-05 15:04 ` Christian Neukirchen
2016-09-05 15:42 ` Peter Stephenson
     [not found]   ` <CGME20160914173110eucas1p1f0567e319ae439b975b19f4e55676fed@eucas1p1.samsung.com>
2016-09-14 17:31     ` Peter Stephenson
2016-09-14 21:35       ` Peter Stephenson
2016-09-15  3:24         ` Bart Schaefer
2016-09-15  8:27           ` Peter Stephenson
2016-09-15 10:33             ` Peter Stephenson
2016-09-15 17:40               ` Peter Stephenson
2016-09-16  1:08                 ` Bart Schaefer
2016-09-16 12:02                   ` Peter Stephenson
2016-09-22 11:59         ` Daniel Shahaf
2016-09-22 16:38           ` Bart Schaefer
2016-09-23  1:18             ` Bart Schaefer [this message]
2016-09-23  6:06               ` Daniel Shahaf
2016-09-25 14:39               ` Peter Stephenson
2016-09-25 22:54                 ` struct job.other (was Re: Bug related to stdin/always/jobcontrol) Bart Schaefer
2016-09-26 11:20                   ` Peter Stephenson
2016-09-26 16:33                     ` Bart Schaefer
2016-09-25 15:16           ` Bug related to stdin/always/jobcontrol Peter Stephenson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=160922181847.ZM22524@torch.brasslantern.com \
    --to=schaefer@brasslantern.com \
    --cc=zsh-workers@zsh.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).