GNOME Bugzilla – Bug 683516
Doxygen crash on process markdown file
Last modified: 2017-09-16 07:12:49 UTC
Doxygen.exe crash if I use \fn or \var I think \class too in markdown files.
Can you please attach a self-contained example (source+config file in a tar or zip) that allows me to reproduce the problem?
Created attachment 223720 [details] Example files
Hello Dimitri. It is easy to reproduce, create markdown file (test.md) and insert: \var int test run doxygen and the application crash. Thanks a lot. Jonas
Thank you for providing a sample for us to work with. In 1.8.3.1, 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.
Version 1.8.2, Windows, x86. But I'm try 1.8.3.1 too, same result.
Can you use a debugger such as Visual Studio.net or gdb to produce a stack trace for us? That will help the doxygen developers see exactly where in the code the crash occurs.
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!
Thanks! That's ok and the result I'm expected (if it the command is not supported in markdown files).
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 Studio.net. The stack trace is unusable because the debugging symbols are not included in the 1.8.3.1 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 Studio.net 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.
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.
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