From: Michael Stapelberg <stapelberg@debian.org>
To: tech@mandoc.bsd.lv
Subject: Re: mandoc 1.14.3 segfault
Date: Tue, 29 Aug 2017 09:04:09 +0200 [thread overview]
Message-ID: <CANnVG6m1_8bJ435rfapfYvj13Fhtuk6V0TiV9DOWcJgA2PdHJg@mail.gmail.com> (raw)
In-Reply-To: <20170812105757.GA34892@www.stare.cz>
Any news on this issue? This is blocking upgrading manpages.debian.org
to the new mandoc release.
On Sat, Aug 12, 2017 at 12:57 PM, Jan Stary <hans@stare.cz> wrote:
> On Aug 12 12:27:32, stapelberg@debian.org wrote:
>> Ib
>> backtrace follow below. Please let me know if you need anything else, and
>> thanks in advance for taking a look:
>>
>> % curl https://manpages.debian.org/stretch/tcpreplay/tcprewrite.1.en.gz |
>> mandoc -Thtml
>
> The curl pipe apparenly has nothing to do with it,
> I can reproduce the sgfault locally with
>
> mandoc -Thtml tcprewrite.1.en.gz
>
> Note that the gzip file is not a gzip file.
> --
> To unsubscribe send an email to tech+unsubscribe@mandoc.bsd.lv
>
--
Best regards,
Michael
--
To unsubscribe send an email to tech+unsubscribe@mandoc.bsd.lv
next prev parent reply other threads:[~2017-08-29 7:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-12 10:27 Michael Stapelberg
2017-08-12 10:57 ` Jan Stary
2017-08-29 7:04 ` Michael Stapelberg [this message]
2017-09-06 16:30 ` Ingo Schwarze
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=CANnVG6m1_8bJ435rfapfYvj13Fhtuk6V0TiV9DOWcJgA2PdHJg@mail.gmail.com \
--to=stapelberg@debian.org \
--cc=tech@mandoc.bsd.lv \
/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.
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).