[FFmpeg-devel] [PATCHv2] ffmpeg: modify tty state when stderr is redirected

[wm4]

On Mon, 12 Oct 2015 08:39:53 -0400
Ganesh Ajjanagadde <gajjanag at mit.edu> wrote:

> On Mon, Oct 12, 2015 at 8:24 AM, wm4 <nfxjfg at googlemail.com> wrote:
> > On Mon, 12 Oct 2015 08:14:14 -0400
> > Ganesh Ajjanagadde <gajjanag at mit.edu> wrote:
> >
> >> On Mon, Oct 12, 2015 at 8:03 AM, Michael Niedermayer
> >> <michael at niedermayer.cc> wrote:
> >> > On Mon, Oct 12, 2015 at 01:46:19PM +0200, Michael Niedermayer wrote:
> >> >> On Fri, Jul 31, 2015 at 01:48:18PM +0200, Nicolas George wrote:
> >> >> [...]
> >> >> >    -> "ttyctl -f" in ~/.zshrc, "bash_tty_mode=$(stty -g);
> >> >> >    PROMPT_COMMAND='stty $bash_tty_mode'" in ~/.bashrc; that can be added in
> >> >> >    the FAQ or the wiki.
> >> >>
> >> >>
> >> >> the patch was applied and this does not work
> >> >>
> >> >> the first segfault i see breaks the terminal
> >> >>
> >> >> a testcase is a script like:
> >> >> #!/bin/sh
> >> >> valgrind ./ffmpeg_g -i matrixbench_mpeg2.mpg -encryption_key 0123456789abcdef0011223344556677  -encryption_iv aabbccddeeff11335577999876542222  crypto:file-crypt.nut
> >> >>
> >> >> (with the aesni patches or anything else that causes a segfault)
> >> >>
> >> >> ls -alF /bin/sh
> >> >> lrwxrwxrwx 1 root root 4 Mar 29  2012 /bin/sh -> dash*
> >> >> (this is default on ubuntu)
> >> >
> >> > i think i got it working as long as bash is the users shell with
> >> > the suggested stty commands
> >>
> >> So it does not work with dash?
> >
> > dash isn't meant to be used interactively anyway?
> 
> Good point, just now read up on this weird shell I have never heard
> of: https://en.wikipedia.org/wiki/Debian_Almquist_shell. However,
> Michael does bring up a point in that /bin/sh by default symlinks to
> dash on a rather large platform, namely Ubuntu. We need to find out a
> workaround for it.  I am of no use here; hopefully Michael finds
> something and posts.
> 
> I will then collect them all and add to the wiki.

No, for interactive shell, Debian and Ubuntu still use bash by default.
So even if /bin/sh is used to run a script, the /bin/sh itself will be
started from a bash. So I do not see the problem here.