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 459726 - [regression] Segfault after reading Doxyfile
[regression] Segfault after reading Doxyfile
Status: RESOLVED FIXED
Product: doxygen
Classification: Other
Component: general
1.5.2
Other Linux
: Normal normal
: ---
Assigned To: Dimitri van Heesch
Dimitri van Heesch
Depends on:
Blocks:
 
 
Reported: 2007-07-23 21:46 UTC by Matthias Klose
Modified: 2007-07-27 09:22 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Doxyfile (45.70 KB, text/plain)
2007-07-23 21:47 UTC, Matthias Klose 		Details

Description Matthias Klose 2007-07-23 21:46:28 UTC 
[forwarded from http://bugs.debian.org/428972]

Bug submitter writes:

While trying to build the documentation for VirtualBox-OSE 1.4.0
(http://virtualbox.org), doxygen gave me a segfault.

,----
| bengen@ataraxia:tmp $ doxygen Doxyfile
| Warning: Tag `USE_WINDOWS_ENCODING' at line 63 of file Doxyfile has become obsolete.
| To avoid this warning please update your configuration file using "doxygen -u"
| Segmentation fault
`----

strace and ltrace show that doxygen only read the control file -- it
did not look at any of the input files.

Commenting out the "USE_WINDOWS_ENCODING" directive does not help -- 
doxygen still segfaults.
Comment 1 Matthias Klose 2007-07-23 21:47:42 UTC 
Created attachment 92230 [details]
Doxyfile
Comment 2 Dimitri van Heesch 2007-07-24 07:54:27 UTC 
This has been fixed in CVS already (unknown or obsoleted tags in the config file caused a crash). I just verified that with doxygen-1.5.2. It indeed crashes while the current CVS version does not.
Comment 3 Dimitri van Heesch 2007-07-27 09:22:48 UTC 
This bug was marked ASSIGNED and as a result has been moved to the FIXED state with the release of 1.5.3, since I believe the bug has been fixed in this release. I kindly ask you to verify this and reopen the bug should this not be the case.