Control: tag -1 fixed-upstream
On Sat, Mar 10, 2018 at 01:20:49PM +0800, Paul Wise wrote:
> On Thu, 2018-03-08 at 13:38 +, Colin Watson wrote:
> > Hmm, this doesn't seem to show a SIGSYS, and man exited 0.
>
> I added some debugging to groff and looked at the code.
>
> It seems that groff pa
On Thu, 2018-03-08 at 13:38 +, Colin Watson wrote:
> Hmm, this doesn't seem to show a SIGSYS, and man exited 0.
I added some debugging to groff and looked at the code.
It seems that groff passes on a SIGPIPE it receives to its children via
kill(pids[j], SIGPIPE) but man-db does not allow it
On Thu, Mar 08, 2018 at 09:25:05PM +0800, Paul Wise wrote:
> On Thu, 2018-03-08 at 10:03 +, Colin Watson wrote:
> > They aren't useful, but I'm not sure why that means I should close
> > the bug.
>
> It is a standard line to get grumpy people who don't like people who
> report crashes to ignor
On Thu, 2018-03-08 at 10:03 +, Colin Watson wrote:
> They aren't useful, but I'm not sure why that means I should close
> the bug.
It is a standard line to get grumpy people who don't like people who
report crashes to ignore them instead of getting grumpy.
> Reassigning to man-db since this
Control: reassign -1 man-db
On Thu, Mar 08, 2018 at 01:07:26PM +0800, Paul Wise wrote:
> I get a crash (SIGSYS) in groff when running `man man | head -n1`.
> If the below output and backtrace are not useful, please close this bug.
They aren't useful, but I'm not sure why that means I should close
Package: groff-base
Version: 1.22.3-10
Severity: normal
File: /usr/bin/groff
Usertags: crash
I get a crash (SIGSYS) in groff when running `man man | head -n1`.
If the below output and backtrace are not useful, please close this bug.
This is unaffected by my setting of MANPATH, MALLOC_CHECK_ & MALL
6 matches
Mail list logo
