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

Include within a block of code causes line numbers to drift and be incorrect (Origin: bugzilla #601222) #3578

doxygen opened this Issue Jul 2, 2018 · 0 comments


None yet
1 participant

doxygen commented Jul 2, 2018

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

Original attachment names and IDs:

On 2009-11-09 08:18:43 +0000, Lucien Murray-Pitts wrote:

Created attachment 147250
Sample source that will exhibit this behaviour

Often when large tables are being used its natural to see a random #include in
the middle of some sources. Doing this with Doxygen will lead to the line
numbers drifting by the number of lines in the included file.

In the code below the include causes the line numbers to slip, this in turn
causes all the call, and/or callee graphs, and any reference line numbers (eg.
"defined at line XX") to become invalid and the DOT package will not
generate/be called to generate the call graphs.

#if 1
// Include some code
int bigtable[ 16 ] =
#include ""
int bigtable[ 16 ] = { 0,0,0,0 } ;

On 2009-11-09 08:20:33 +0000, Lucien Murray-Pitts wrote:

I am using the following setup;
Doxy 1.6.1 for Windows, under WinXP SP3 - 32bits, Pentium4 Centrino
Compiled using Vis. Studio Express 2008, cl.exe mainfile.cpp

On 2009-11-10 19:46:11 +0000, Dimitri van Heesch wrote:

Confirmed. Doxygen can already handle such #include's but not when embedded inside a class. Should be fixed in the next subversion update.

On 2009-12-30 13:38:30 +0000, Dimitri van Heesch wrote:

This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.6.2. Please verify if this is indeed the case and reopen the
bug if you think it is not fixed (include any additional information that you
think can be relevant).

@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