New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

@code tag as the last line of a comment block causes the parser to hang (Origin: bugzilla #705586) #5260

Closed
doxygen opened this Issue Jul 2, 2018 · 0 comments

Comments

Projects
None yet
1 participant
@doxygen
Owner

doxygen commented Jul 2, 2018

status RESOLVED severity normal in component build for ---
Reported in version 1.8.4 on platform Other
Assigned to: Dimitri van Heesch

Original attachment names and IDs:

On 2013-08-06 18:33:44 +0000, aarp@sjm.com wrote:

Created attachment 250996
Simple C# program and doxygen config file exhibiting problem

In some unique situations, having a @code tag as the last line of a comment block causes the parser to hang. See the attached C# project files and Doxygen configuration file that reproduces this issue.

Additionally, if this configuration file is run from the Doxygen GUI, the last few lines of output before the hang are:
Parsing files
Preprocessing C:/SourceCode/DoxygenTest/DoxygenTest/Program.cs...
Parsing file C:/SourceCode/DoxygenTest/DoxygenTest/Program.cs...

However, if run from a command prompt, the last few lines before the hang are:
Parsing files
Preprocessing C:/SourceCode/DoxygenTest/DoxygenTest/Program.cs...
Parsing file C:/SourceCode/DoxygenTest/DoxygenTest/Program.cs...
C:/SourceCode/DoxygenTest/DoxygenTest/Program.cs:29: Warning: reached end of comment while inside a @code block; check for missing @Endcode tag!

It appears to be detecting the missing @Endcode, but not recovering properly.

The comment block that causes the hang is:
///


/// This is a test case for Doxygen
///

///
/// \code

Having another line of 3-slash comments after the \code line will cause the parser to behave properly.

On 2013-08-06 18:51:01 +0000, Dimitri van Heesch wrote:

Confirmed. Should be fixed in the next GIT update.
As a workaround you could set MARKDOWN_SUPPORT to NO.

On 2013-08-23 15:04:30 +0000, Dimitri van Heesch wrote:

This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.8.5. 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.

@doxygen doxygen closed this Jul 2, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment