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

`FILTER_SOURCE_FILES=YES` required to build CALL_GRAPHS (Origin: bugzilla #707641) #5289

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

Comments

Projects
None yet
1 participant
@doxygen
Owner

doxygen commented Jul 2, 2018

status RESOLVED severity normal in component general for ---
Reported in version 1.8.5-GIT on platform Other
Assigned to: Dimitri van Heesch

Original attachment names and IDs:

On 2013-09-06 16:21:38 +0000, Sergio Oller wrote:

Created attachment 254273
A script to reproduce the bug

Bug report: FILTER_SOURCE_FILES=YES required to build CALL_GRAPHS

CALL/CALLER graphs are not created if FILTER_SOURCE_FILES=NO and a filter is used.

It is not possible to view the graphs and browse the original source files at the same time.

Attached is a tgz file with a sample code, a sample filter and a script which will reproduce the error.

Reproduce the error:

When running the attached ./test_error.sh, two output directories are created:

  • works_fine shows the CALL_GRAPHS and CALLER_GRAPHS properly
    at the expense of browsing the filtered sources (I prefer the unfiltered version).

  • no_caller_graphs fails to generate the CALL_GRAPHS and CALLER_GRAPHS.
    The only difference in the setup is: FILTER_SOURCE_FILES = NO.
    I would expect to browse the unfiltered source files but to be able to
    see the call graphs.

Thanks in advance for any support. Any help or suggestion will be appreciated.

Sergio

On 2013-09-14 18:24:32 +0000, Sergio Oller wrote:

Pull request to fix this bug available at:

#35

On 2013-09-28 22:08:42 +0000, Dimitri van Heesch wrote:

Thanks, I'll include an improved version of your patch in the next GIT update.

On 2013-12-24 19:00:12 +0000, Dimitri van Heesch wrote:

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