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 682048 - Interrupting doxygen during graph creation spews PNG output to console
Interrupting doxygen during graph creation spews PNG output to console
Status: RESOLVED FIXED
Product: doxygen
Classification: Other
Component: general
1.8.1.1
Other Linux
: Normal normal
: ---
Assigned To: Dimitri van Heesch
Dimitri van Heesch
Depends on:
Blocks:
 
 
Reported: 2012-08-16 22:24 UTC by Elliott Sales de Andrade
Modified: 2012-12-26 16:08 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Elliott Sales de Andrade 2012-08-16 22:24:47 UTC 
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.
Comment 1 Elliott Sales de Andrade 2012-08-16 22:30:12 UTC 
Also can still reproduce with 1.8.1.1.
Comment 2 Dimitri van Heesch 2012-08-19 16:01:57 UTC 
I haven't been able to reproduce this completely, but I have improved SIGINT handling, so that would hopefully prevent this behaviour.
Comment 3 Dimitri van Heesch 2012-12-26 16:08:57 UTC 
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.