#2144 Rejected entry crashes makeindex if not first

None
fixed
makeindex (7)
2016-04-21
2012-05-07
No

$ tex --version
MiKTeX-TeX 2.9.3759 (3.1415926) (MiKTeX 2.9)

With the attached file, run:

$ makeindex crash.idx

And makeindex will crash. I get a dialog saying "General Purpose Index Processor has stopped working" in my locale.

The file crash.idx has two index entries in it. If I remove the first entry, the remaining entry is rejected:

!! Input index error (file = refman.idx, line = 1):
-- First argument too long (max 1024).

As far as I can tell, the problem is that the last character in the argument, when truncated to 1024 characters, is a backslash. Other characters at that position do not trigger the crash.

I don't know why it matters that this index entry is not first. Any other position in the list of index entries will trigger the crash.

Discussion

  • Ryan Phillips

    Ryan Phillips - 2012-05-07
     
  • Maarten Brock

    Maarten Brock - 2014-10-02

    I think I experience the same or a similar bug. My file is generated by doxygen and contains lines upto 4607 characters and with lots of backslashes.

    MiKTeX-TeX 2.9.3759 (3.1415926) (MiKTeX 2.9 64-bit)

    If there is anything I can do to get this fixed please say so. But please try to fix this.

     
    • Albert

      Albert - 2014-11-25

      Might be a known problem in doxygen. Please have a look at the git version of doxygen, here Bug 733323 - Doxygen generated LaTeX leads to General Purpose Index Processor crash (https://bugzilla.gnome.org/show_bug.cgi?id=733323) has been integrated.

       
  • Maarten Brock

    Maarten Brock - 2014-11-25

    Are you saying that doxygen generated illegal input files for MiKTeX? Or that it now knows how to work around a bug in MiKTeX?

     
    • Albert

      Albert - 2014-11-25

      The generated output of doxygen didn't have problems with the Linux distribution I used but crashed on Windows with MiKTeX. So I'm not sure if it was an illegal generated input file and that the Linux distribution was more lenient. The code was not clean as far I could see so this has been corrected.

       
  • Christian Schenk

    • Owner: Anonymous --> Christian Schenk
    • Status: open --> attic
     
    • Maarten Brock

      Maarten Brock - 2016-04-20

      Does this mean that this problem is fixed in a later version?

       
  • Christian Schenk

    • status: attic --> fixed
    • Milestone: --> None
     
  • Christian Schenk

    This has been fixed in the course of development, i.e., I cannot reproduce the crash with the latest version (MiKTeX NEXT).