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 702590 - Crash with TAB_SIZE=-1
Crash with TAB_SIZE=-1
Status: VERIFIED FIXED
Product: doxygen
Classification: Other
Component: general
1.8.4
Other Windows
: High major
: ---
Assigned To: Dimitri van Heesch
Dimitri van Heesch
Depends on:
Blocks:
 
 
Reported: 2013-06-18 18:31 UTC by albert
Modified: 2013-08-23 16:58 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Source file and Doxyfile to reproduce bug (23.01 KB, application/octet-stream)
2013-06-18 18:35 UTC, albert
Details

Description albert 2013-06-18 18:31:57 UTC
I tried TAB_SIZE = -1 (version 1.8.4 on windows) and got a crash (Doxyfile is further a standard Doxyfile). When trying my local version under cygwin I got:
Warning: argument `-1' for option TAB_SIZE is not a valid number in the range [1..16]!
Using the default: 4!

Program received signal SIGSEGV, Segmentation fault.
0x004211c7 in adjustConfiguration() ()
(gdb) where
  • #0 adjustConfiguration()
  • #1 main
  • #0 commentcnvYYlex()
  • #1 convertCppComments(BufStr*, BufStr*, char const*)
  • #2 parseFiles(Entry*, EntryNav*)
  • #3 parseInput()
  • #4 main



Source code:
/** @file aa.c
 * docu aa
 */


/** @brief docu fie
 */
void fie(void)
{
        int i;
}

(NOTE: before int i; is a <tab>)
Comment 1 albert 2013-06-18 18:35:25 UTC
Created attachment 247201 [details]
Source file and Doxyfile to reproduce bug
Comment 2 Dimitri van Heesch 2013-06-18 18:59:16 UTC
Confirmed. Should be fixed in the next GIT update.
Comment 3 Dimitri van Heesch 2013-08-23 15:04:46 UTC
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.
Comment 4 albert 2013-08-23 16:58:17 UTC
Boundaries of TAB_SIZE are handled correctly now.