From: Ingo Schwarze <schwarze@usta.de>
To: "Ulrich Spörlein" <uqs@spoerlein.net>
Cc: discuss@mdocml.bsd.lv
Subject: Re: Crash in makewhatis on FreeBSD's man9 manuals
Date: Sat, 16 Aug 2014 22:02:01 +0200 [thread overview]
Message-ID: <20140816200201.GB12335@iris.usta.de> (raw)
In-Reply-To: <20140816175602.GA17988@elmar.spoerlein.net>
Hi Ulrich,
Ulrich Spörlein wrote on Sat, Aug 16, 2014 at 07:56:03PM +0200:
> 0x0000000000410ba6 in post_it (mdoc=0x801819200) at mdoc_validate.c:1209
> 1209 lt = nbl->norm->Bl.type;
Ouch.
Thanks for the precise report. Having that snippet and the manual,
i didn't even need to fire up my debugger.
It's a weird thing. These manuals use .It as the first macro *after*
lists - as opposed to *inside* lists. Now the code thought, "great,
the last thing i saw was a list, so the list item is probably at
about the right place here." Well, not quite...
You probably saw the fix i just committed, a three-line diff to
mdoc_macro.c.
Yours,
Ingo
--
To unsubscribe send an email to discuss+unsubscribe@mdocml.bsd.lv
prev parent reply other threads:[~2014-08-16 20:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-16 17:56 Ulrich Spörlein
2014-08-16 20:02 ` Ingo Schwarze [this message]
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=20140816200201.GB12335@iris.usta.de \
--to=schwarze@usta.de \
--cc=discuss@mdocml.bsd.lv \
--cc=uqs@spoerlein.net \
/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).