Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

QGDict::hashAsciiKey: Invalid null key (Origin: bugzilla #735037) #5551

Closed
doxygen opened this Issue Jul 2, 2018 · 0 comments

Comments

Projects
None yet
1 participant
@doxygen
Copy link
Owner

doxygen commented Jul 2, 2018

status RESOLVED severity normal in component documentation for ---
Reported in version 1.8.6 on platform Other
Assigned to: Dimitri van Heesch

Original attachment names and IDs:

On 2014-08-19 08:22:26 +0000, pdaouadi@aldebaran.com wrote:

How to reproduce:

  • doxygen -g
  • change the file to set
    PREDEFINED= MYMACRO(...)=
  • doxygen

Result:
An infinite loop of
QGDict::hashAsciiKey: Invalid null key

On 2014-08-19 09:59:28 +0000, Dimitri van Heesch wrote:

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?

On 2014-08-19 14:13:58 +0000, pdaouadi@aldebaran.com wrote:

Created attachment 283897
Minimal test

On 2014-08-19 14:16:06 +0000, pdaouadi@aldebaran.com wrote:

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 ?

On 2014-08-20 10:17:27 +0000, Dimitri van Heesch wrote:

Confirmed. Should be fixed in the next GIT update.

On 2014-08-21 17:15:32 +0000, Dimitri van Heesch wrote:

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).

@doxygen doxygen closed this Jul 2, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.