Red Hat Bugzilla – Bug 365771
doxygen segfaults reading doxygen.cfg
Last modified: 2008-01-04 12:01:55 EST
Description of problem:
I recently upgraded my server from FC4 to F7. One of my daily tasks is running
doxygen to build the nightly documentation for the project. When I first
upgraded, doxygen was throwing a bunch of warnings every night due to deprecated
configuration parameters. After updating the configuration doxygen now crashes
every time it's run! Here's the stack trace:
Program received signal SIGSEGV, Segmentation fault.
QCString::assign (this=0x14, str=0x8f7e3d8 "UTF-8") at scstring.cpp:87
87 if (m_data) free(m_data);
(gdb) p m_data
Cannot access memory at address 0x14
#0 QCString::assign (this=0x14, str=0x8f7e3d8 "UTF-8") at scstring.cpp:87
#1 0x082be511 in configYYlex () at ../qtools/qcstring.h:316
#2 0x082c4582 in Config::parseString (this=0x8f69358,
str=0x8f8bce0 "# Doxyfile 1.5.3-20071008\n\n# This file describes the
settings to be used by the documentation system\n# doxygen (www.doxygen.org) for
a project\n#\n# All text after a hash (#) is considered a comment and"...)
#3 0x082c4720 in Config::parse (this=0x8f69358, fn=0xbf978b62 "doxygen.cfg")
#4 0x0806cbc4 in readConfiguration (argc=2, argv=0xbf977ba4)
#5 0x08049c8f in main (argc=Cannot access memory at address 0xe5d5b36
) at main.cpp:35
#6 0x002ddf70 in __libc_start_main () from /lib/libc.so.6
#7 0x08049bd1 in _start ()
Version-Release number of selected component (if applicable):
Appears to be completely reproducible with the current gnucash configuration
(which I've attached). If you want I can explain how to reconfigure the sources
out of SVN such that you'll get the current doxygen config.
Steps to Reproduce:
1. run doxygen against the config
2. watch it die a flaming death
3. cry, because your script deleted the html output already and now you have no
SEGV. See the backtrace above.
Nice, pretty documentation based on our sources.
See attached config file.
Created attachment 247581 [details]
Configuration file that causes doxygen crash
Apparently this bug is fixed in 1.5.3:
Maybe you could push out an update?
I can confirm this with current F-8:
$ rpm -q doxygen
$ echo "QT_AUTOBRIEF = NO" | doxygen -
I can see 1.5.3 builds in koji. Would you mind pushing those through the updates
*** This bug has been marked as a duplicate of 262041 ***