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

Bogus message with addtogroup (Origin: bugzilla #742235) #5705

doxygen opened this Issue Jul 2, 2018 · 0 comments


None yet
1 participant

doxygen commented Jul 2, 2018

status VERIFIED severity normal in component build for ---
Reported in version 1.8.9 on platform Other
Assigned to: Dimitri van Heesch

Original attachment names and IDs:

On 2015-01-02 18:57:26 +0000, albert wrote:

Created attachment 293614
Input files aa.h and bb.h

When having a group mentioned twice was part of another group (see example aa.h) we get the message:
aa.h:18: warning: Refusing to add group lvl2 to group lvl1, since the latter is already a subgroup of the former

According to the documentation this should be possible, the message is given and the output looks OK. With version 1.8.8 we didn't get the a warning.

Furthermore in the file bb.h the same situation is depicted and we get in 1.8.9 a warning message (as we should according the documentation) but in version 1.8.8 we didn't get the message. Output looks OK again.

Problem is probably introduced with change:
Debian Bug 762272: segfault with cyclic subgroups [ c83db38]

On 2015-01-03 22:33:37 +0000, Dimitri van Heesch wrote:

Confirmed. Should be fixed in the next GIT update.

On 2015-01-04 13:19:41 +0000, Dimitri van Heesch wrote:

This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 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).

On 2015-01-04 14:36:02 +0000, albert wrote:

Bogus message disappeared.

@doxygen doxygen closed this Jul 19, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment