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 318208 - include graph has wrong links
include graph has wrong links
Status: VERIFIED FIXED
Product: doxygen
Classification: Other
Component: general
1.4.x
Other Windows
: Normal normal
: ---
Assigned To: Dimitri van Heesch
Dimitri van Heesch
Depends on:
Blocks:
 
 
Reported: 2005-10-07 15:20 UTC by Nikolay
Modified: 2006-01-01 15:35 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
the doxyfile I am using to generate the sources (9.43 KB, text/plain)
2005-10-07 15:31 UTC, Nikolay 		Details
screen shot of visual studio (118.72 KB, image/jpeg)
2005-12-31 14:40 UTC, Nikolay 		Details
screen shot in debug mode (167.77 KB, image/jpeg)
2005-12-31 15:18 UTC, Nikolay 		Details

Description Nikolay 2005-10-07 15:20:34 UTC 
In Doxygen 1.4.5 the graph at the top of each file which displays the dependancy
graph seems to be generated with the wrong links. For example in one of my files
it generates the link:
Doxygen/d2/d79/a16584-source.html

however that doesn't exist it should be:
Doxygen/d2/d79/a16584.html
Comment 1 Nikolay 2005-10-07 15:31:18 UTC 
Created attachment 53186 [details]
the doxyfile I am using to generate the sources
Comment 2 Dimitri van Heesch 2005-10-09 16:25:04 UTC 
Confirmed. With CREATE_SUBDIRS enabled, there were no less than 3 issues with
the output and the include dependency graphs. Should all be fixed in the next
CVS update.
Comment 3 Dimitri van Heesch 2005-12-30 17:47:50 UTC 
This bug had the status ASSIGNED (which meant it was fixed, but not officially released), so now doxygen release 1.4.6 is out I've given it the status FIXED. 

Nevertheless, I would like to ask you to verify that this bug is indeed fixed in release 1.4.6. If not, then please reopen the bug.
Comment 4 Nikolay 2005-12-31 14:40:02 UTC 
I cannot verify this bug because doxygen crashes when I run it against our code. I am not sure how to debug this crash. I can attach a screen shot of visual studio debugging the doxygen.exe
Comment 5 Nikolay 2005-12-31 14:40:55 UTC 
Created attachment 56594 [details]
screen shot of visual studio
Comment 6 Kevin McBride 2005-12-31 14:56:10 UTC 
Did you try compiling doxygen from the source, under the Debug configuration?  That's the easiest way to debug doxygen problems under Windows.
Comment 7 Nikolay 2005-12-31 15:17:56 UTC 
Well.. I have just now compiled it in debug mode. As I have no experience with the doxygen codebase I am none the wiser. I can however attach a better screen shot showing the stack trace.
Comment 8 Nikolay 2005-12-31 15:18:47 UTC 
Created attachment 56596 [details]
screen shot in debug mode
Comment 9 Dimitri van Heesch 2005-12-31 15:38:32 UTC 
From the screenshot it looks like the system crashed when doing a malloc of 12 bytes! This is strange. It could mean that
1) there is no more memory in the system (or at least available to the doxygen process).
2) due to some form of memory corruption the malloc library fails.

If you can run a tool such as BoundsChecker or Purify that might give a better indication of what is wrong. If you can reproduce this in a small(er) example that you can sent to me I can also analyse the problem in more detail for you.
Comment 10 Nikolay 2006-01-01 15:35:30 UTC 
With the patch that was e-mail to me by Dimitry I can confirm that 1.4.6 fixes this problem.