On Sun, Feb 18, 2018 at 07:22:01PM -0500, John Sivak wrote:
> On 02/18/2018 04:50 PM, Colin Watson wrote:
> > Any information at all would be good. :-)  Could you start by running
> > the relevant man command line under "strace -f -o man.trace -s 1024" and
> > attaching the resulting man.trace file?
> Attached is the trace for the command "strace -f -o man.trace -s 1024
> man man".

(For the record, this is entirely unrelated to the original report

Do you have an unusual libc or a modified libpipeline or something?  The
sequence of system calls that your trace shows at the point where
libpipeline should be calling execvp for nroff doesn't correspond to any
libc implementation I can find, and the failure comes when it tries to
open a Unix-domain socket in the middle of the execvp sequence which is
just weird.

Colin Watson                                       [cjwat...@debian.org]

Reply via email to