After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 680575 - the program crashes with <code> tag in a specific case
the program crashes with <code> tag in a specific case
Status: RESOLVED FIXED
Product: doxygen
Classification: Other
Component: general
1.8.1.2-SVN
Other Windows
: Normal critical
: ---
Assigned To: Dimitri van Heesch
Dimitri van Heesch
Depends on:
Blocks:
 
 
Reported: 2012-07-25 09:08 UTC by alessandro.battini
Modified: 2012-08-20 15:16 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
documents to test the bug (80.00 KB, application/octet-stream)
2012-07-25 09:09 UTC, alessandro.battini 		Details

Description alessandro.battini 2012-07-25 09:08:10 UTC 
See the attached tar
In the file "not_working.cs" there is a documented class with some code, if I try to generate documentation the programa crashes.
I can see the line "Generating annotated compound index..." and the crashes.

After some investigation I added an empty comment line after line 10, "working.cs" 
between the comment and the <case> tag, in this way doxygen ends the creation of the documentation.

In attachement there is also the configuration file I used, I did not check if with base configuration the program hangs or not.

The problem occurs either compiling the SVN version on windows(32 and 64 bit) and also using the stable version.
Comment 1 alessandro.battini 2012-07-25 09:09:38 UTC 
Created attachment 219618 [details]
documents to test the bug
Comment 2 Dimitri van Heesch 2012-07-27 11:56:55 UTC 
Confirmed. Should be fixed in the next subversion update.
Comment 3 Dimitri van Heesch 2012-08-11 13:18:14 UTC 
This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.8.2. Please verify if this is indeed the case. Reopen the
bug if you think it is not fixed and please include any additional information
that you think can be relevant.
Comment 4 alessandro.battini 2012-08-20 15:16:22 UTC 
I have made a check, the bug is solved.
I've tried both 1.8.2 downloaded and svn in Windows.