Skip to content
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

Doxygen crash on process markdown file (Origin: bugzilla #683516) #4877

doxygen opened this Issue Jul 2, 2018 · 0 comments


None yet
1 participant
Copy link

doxygen commented Jul 2, 2018

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

Original attachment names and IDs:

On 2012-09-06 16:18:01 +0000, Jonas wrote:

Doxygen.exe crash if I use \fn or \var I think \class too in markdown files.

On 2012-09-06 18:20:30 +0000, Dimitri van Heesch wrote:

Can you please attach a self-contained example (source+config file in a tar or zip) that allows me to reproduce the problem?

On 2012-09-07 05:09:06 +0000, Jonas wrote:

Created attachment 223720
Example files

On 2012-09-07 05:14:47 +0000, Jonas wrote:

Hello Dimitri.

It is easy to reproduce, create markdown file ( and insert:

\var int test

run doxygen and the application crash.

Thanks a lot.

On 2013-04-07 00:57:54 +0000, Kevin McBride wrote:

Thank you for providing a sample for us to work with.

In, there is no segfault happening with doxygen. Being that this bug has version number as unspecified, I am closing this bug as "incomplete." If you can, please specify the doxygen version you used so that we can decide if the resolution needs changing.

On 2013-04-07 07:32:11 +0000, Jonas wrote:

Version 1.8.2, Windows, x86. But I'm try too, same result.

On 2013-04-07 14:47:34 +0000, Kevin McBride wrote:

Can you use a debugger such as Visual or gdb to produce a stack trace for us? That will help the doxygen developers see exactly where in the code the crash occurs.

On 2013-04-07 15:31:40 +0000, Dimitri van Heesch wrote:

Confirmed. Should be fixed in the next subversion update.

Note that .md are for Markdown markup only. Markup related doxygen commands like \c and \ref are also supported, but not structural commands like \var or \class, so these will simply be ignored!

On 2013-04-07 17:48:02 +0000, Jonas wrote:

Thanks! That's ok and the result I'm expected (if it the command is not supported in markdown files).

On 2013-04-07 20:46:16 +0000, Kevin McBride wrote:

I created a link to a command prompt manually on my Windows 8 laptop "C:\Windows\System32\cmd.exe" and ran doxygen manually that way. I got a popup that allowed me to open Visual The stack trace is unusable because the debugging symbols are not included in the release. If I manage to get a usable stack trace for this bug, I will attach one. I will have to compile doxygen manually with Visual with debugging symbols.

In addition, I made this bug dependent on a new bug I filed, in hopes that the doxywizard will let me open up a debugger so that stack traces can be attached to bug reports.

On 2013-05-19 12:36:06 +0000, Dimitri van Heesch wrote:

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

On 2017-09-16 07:12:49 +0000, wrote:

Hello, I'm in trouble with Markdown file.

When there is a '@file filename' in markdown file, doxygen seems to stop generating html. Also in fenced code block.
'@bfief brief' command, does not cause doxygen stop, but generated html are strange.

Doxygen 1.8.13 on Windows 10 x64

@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
You can’t perform that action at this time.