discuss@mandoc.bsd.lv
 help / color / mirror / Atom feed
From: Stephen Gregoratto <dev@sgregoratto.me>
To: discuss@mandoc.bsd.lv
Subject: Assert fails when outputting mdoc -> man with EQN
Date: Sun, 16 Feb 2020 01:28:07 +1100	[thread overview]
Message-ID: <20200215142807.xsiwplllqpp735yg@dextop.sgregoratto.me> (raw)

I recently forked a simple password generator[1] and converted some
equations in the manpage[2] to eqn. For some reason, converting from
mdoc to man triggers an assertion (from the latest CVS revision):

mdoc_man.c:301: mdoc_man_act: Assertion `tok >= MDOC_Dd && tok <= MDOC_MAX' failed.

Inspecting it in GDB, we see that:

(gdb) p tok
$4 = TOKEN_NONE

[1] https://git.sgregoratto.me/rpass/
[2] https://www.sgregoratto.me/paste/rpass.1
-- 
Stephen Gregoratto
--
 To unsubscribe send an email to discuss+unsubscribe@mandoc.bsd.lv

             reply	other threads:[~2020-02-15 14:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-15 14:28 Stephen Gregoratto [this message]
2020-02-15 15:17 ` 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=20200215142807.xsiwplllqpp735yg@dextop.sgregoratto.me \
    --to=dev@sgregoratto.me \
    --cc=discuss@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).