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 742715 - Unnamed structs gives: QGDict::hashAsciiKey: Invalid null key
Unnamed structs gives: QGDict::hashAsciiKey: Invalid null key
Status: VERIFIED FIXED
Product: doxygen
Classification: Other
Component: documentation
1.8.9.1
Other Windows
: Normal normal
: ---
Assigned To: Dimitri van Heesch
Dimitri van Heesch
Depends on:
Blocks:
 
 
Reported: 2015-01-10 17:41 UTC by albert
Modified: 2015-12-31 10:21 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Source file and Doxyfile to reproduce problem (26.66 KB, application/octet-stream)
2015-01-10 17:44 UTC, albert 		Details

Description albert 2015-01-10 17:41:20 UTC 
In case of an unnamed struct inside another struct one get messages about: QGDict::hashAsciiKey: Invalid null key

The attached small example gives:
...
Generating group documentation...
Generating class documentation...
Generating docs for compound s1...
QGDict::hashAsciiKey: Invalid null key
QGDict::hashAsciiKey: Invalid null key
Generating namespace index...
Generating graph info page...
...
Comment 1 albert 2015-01-10 17:44:26 UTC 
Created attachment 294234 [details]
Source file and Doxyfile to reproduce problem

Attachment adding did go wrong first time.
Comment 2 Dimitri van Heesch 2015-12-27 10:24:09 UTC 
I don't see this problem; neither with 1.8.9.1 nor with the latest version of doxygen. Can you double check it still occurs and is indeed triggered by the example provided?
Comment 3 albert 2015-12-27 10:33:06 UTC 
I just tried it, on Windows, with 1.8.9.1, 1.8.10 and the current git version and the problem is still present.
Comment 4 Dimitri van Heesch 2015-12-28 19:57:33 UTC 
Confirmed. Should be fixed in the next GIT update.
Comment 5 Dimitri van Heesch 2015-12-30 10:20:01 UTC 
This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.8.11. 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 (preferably in the form of a self-contained example).
Comment 6 albert 2015-12-31 10:21:13 UTC 
Messages are gone now.