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

Interrupting doxygen during graph creation spews PNG output to console (Origin: bugzilla #682048) #4853

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.1.1 on platform Other
Assigned to: Dimitri van Heesch

On 2012-08-16 22:24:47 +0000, Elliott Sales de Andrade wrote:

If you interrupt doxygen while it's creating the PNG call graphs, then you get the PNG output to the console in binary form.

Not only is it a bunch of gibberish, it sometimes messes with the console settings for fonts and colours and such. Additionally, since they're not immediate children of the shell, you can't interrupt them with another Ctrl+C.

It seems like the main doxygen process closes, but doesn't cancel any of the graph processes, which spew to console, since their parent is gone.

Steps to Reproduce:

  1. Start a Doxyfile with call graphs enabled.
  2. Run doxygen.
  3. Hit Ctrl+C when it gets to the graph creation step.

Actual results:
The binary PNG data is printed on the console.

Expected results:
doxygen should exit without any extraneous output.

On 2012-08-16 22:30:12 +0000, Elliott Sales de Andrade wrote:

Also can still reproduce with 1.8.1.1.

On 2012-08-19 16:01:57 +0000, Dimitri van Heesch wrote:

I haven't been able to reproduce this completely, but I have improved SIGINT handling, so that would hopefully prevent this behaviour.

On 2012-12-26 16:08:57 +0000, Dimitri van Heesch wrote:

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

@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