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 743920 - tagfile lists functions in the wrong classes.
tagfile lists functions in the wrong classes.
Status: RESOLVED FIXED
Product: doxygen
Classification: Other
Component: general
1.8.9.1
Other Linux
: Normal normal
: ---
Assigned To: Dimitri van Heesch
Dimitri van Heesch
Depends on:
Blocks: 743918
 
 
Reported: 2015-02-03 10:48 UTC by Murray Cumming
Modified: 2015-02-11 15:04 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Murray Cumming 2015-02-03 10:48:30 UTC
I've noticed that gtkmm's tagfile has functions listed under the wrong classes. For instance, all the Gtk::Window and Gtk::Dialog member methods are listed under Gtk::AboutDialog (which derives from Gtk::Dialog, which derives from Gtk::Window).

I don't know what's triggering this yet, but there are some more clues in our gtkmm bug #743918 .
Comment 1 Dimitri van Heesch 2015-02-08 09:00:40 UTC
Could you check if this still happens with the lastest snapshot from GitHub (I've pushed two tag files related fixes), and if so provide a self-contained example (or stepwise instructions) on how I can reproduce this bug?
Comment 2 Kjell Ahlstedt 2015-02-08 11:42:03 UTC
I believe that this is the problem described in bug 707971 and bug 736992.
I generated gtkmm's tagfile with different versions of doxygen. It looks like
the bug is absent in doxygen 1.8.9 and 1.8.9.1, probably fixed when bug 736992
was fixed.

But this bug is filed against doxygen 1.8.9.1, so perhaps it still pops up in
rare cases. Murray, I tested both with and without your fix in
https://git.gnome.org/browse/gtkmm/commit/?id=00fa70e71b2637735360cce56f9f1bc2afc8674a
In both cases the tag file looks ok with doxygen 1.8.9 and 1.8.9.1, but it's
wrong with doxygen 1.8.7.
Comment 3 Murray Cumming 2015-02-10 08:30:43 UTC
Were you using gtkmm from git with my #ifdefing workaround commit?

I checked with the latest tarball (doxygen 1.8.9.1) as well as my regular version in Ubuntu (1.8.8) and didn't see any change in the problem. But I suppose it's possible that I was using the wrong one at some time.

It was really hard to figure out what was causing the problem and I'm not confident I can come up with a simple test case. Sorry for being lazy, but let's indeed assume that it's fixed.
Comment 4 Kjell Ahlstedt 2015-02-11 15:04:14 UTC
I have reported some results in bug 743918 comment 4.