Package: halibut
Version: 1.2-2
(I didn't find a bug tracker for Halibut upstream, so I'm reporting this
here and I put Simon Tatham / you into the CC.)
A simple test file, in two variants, causes a segmentation fault either
when outputting --chm (in both variants), or when outputting --html
(only in the variant with a non-resolving cross-reference included).
===
~/test/halibug$ halibut --version
Halibut, version 1.2
~/test/halibug$ cat test1.src
\cfg{chapter}{Section}
\b If \c{EAX} is zero on input, \c{EAX} on output holds the maximum
acceptable input value of \c{EAX}, and \c{EBX:EDX:ECX} contain the
string \c{"GenuineIntel"} (or not, if you have a clone processor).
That is to say, \c{EBX} contains \c{"Genu"} (in NASM's own sense of
character constants, described in \k{chrconst}), \c{EDX} contains
\c{"ineI"} and \c{ECX} contains \c{"ntel"}.
~/test/halibug$ halibut --precise test1.src --chm
test1.src:7:35: unable to resolve cross-reference to `chrconst'
test1.src:7:35: unable to resolve cross-reference to `chrconst'
Segmentation fault
~/test/halibug$ halibut --precise test1.src --html
test1.src:7:35: unable to resolve cross-reference to `chrconst'
test1.src:7:35: unable to resolve cross-reference to `chrconst'
Segmentation fault
~/test/halibug$ cat test1.src
\cfg{chapter}{Section}
\b If \c{EAX} is zero on input, \c{EAX} on output holds the maximum
acceptable input value of \c{EAX}, and \c{EBX:EDX:ECX} contain the
string \c{"GenuineIntel"} (or not, if you have a clone processor).
That is to say, \c{EBX} contains \c{"Genu"} (in NASM's own sense of
character constants\#{, described in \k{chrconst}}), \c{EDX} contains
\c{"ineI"} and \c{ECX} contains \c{"ntel"}.
~/test/halibug$ halibut --precise test1.src --chm
Segmentation fault
~/test/halibug$ halibut --precise test1.src --html
~/test/halibug$ xdg-open test1.htm
~/test/halibug$
===
Regards,
ecm
