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 735037 - QGDict::hashAsciiKey: Invalid null key
QGDict::hashAsciiKey: Invalid null key
Status: RESOLVED FIXED
Product: doxygen
Classification: Other
Component: documentation
1.8.6
Other Linux
: Normal normal
: ---
Assigned To: Dimitri van Heesch
Dimitri van Heesch
Depends on:
Blocks:
 
 
Reported: 2014-08-19 08:22 UTC by pdaouadi
Modified: 2014-08-21 17:15 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Minimal test (22.12 KB, application/x-bzip2)
2014-08-19 14:13 UTC, pdaouadi 		Details

Description pdaouadi 2014-08-19 08:22:26 UTC 
How to reproduce:
- doxygen -g
- change the file to set
PREDEFINED= MYMACRO(...)=
- doxygen

Result:
An infinite loop of
QGDict::hashAsciiKey: Invalid null key
Comment 1 Dimitri van Heesch 2014-08-19 09:59:28 UTC 
I guess I would need some source file as well in order to trigger this? (without it I see no issues). And the ... in MYMACRO(...) is not supported, you need to specify a list of variables.

So can you please check if the problem still occurs in 1.8.7, and if so attach a self-contained example (source+config file in a tar or zip) that allows me to reproduce the problem?
Comment 2 pdaouadi 2014-08-19 14:13:58 UTC 
Created attachment 283897 [details]
Minimal test
Comment 3 pdaouadi 2014-08-19 14:16:06 UTC 
Thanks for your response.

Indeed, you need a file, just touch a.c is enough.

I reproduced the bug with the git master version.

If "..." is not supported, is there a recommended workaround? Should I include something like
#ifdef DOXYGEN
#define MYMACRO(...)
#endif
in my code ?
Comment 4 Dimitri van Heesch 2014-08-20 10:17:27 UTC 
Confirmed. Should be fixed in the next GIT update.
Comment 5 Dimitri van Heesch 2014-08-21 17:15:32 UTC 
This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.8.8. 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 (preferrably in the form of a self-contained example).