Leaving musescore3 Appimage : some strange info is printed on the terminal
I'm running mscore-3 Appimage (871c8ce) . If I leave mscore then mscore3 prints some strange info on the terminal where I started it:
profiling:/MuseScore:Cannot create directory
profiling:/MuseScore/build.release/libmscore/CMakeFiles/libmscore.dir/elementlayout.gcda:Skip
profiling:/MuseScore:Cannot create directory
profiling:/MuseScore/build.release/libmscore/CMakeFiles/libmscore.dir/bsp.gcda:Skip
profiling:/MuseScore:Cannot create directory
profiling:/MuseScore/build.release/libmscore/CMakeFiles/libmscore.dir/plugins.gcda:Skip
profiling:/MuseScore:Cannot create directory
profiling:/MuseScore/build.release/libmscore/CMakeFiles/libmscore.dir/libmscore_automoc.gcda:Skip
profiling:/MuseScore:Cannot create directory
profiling:/MuseScore/build.release/libmscore/CMakeFiles/libmscore.dir/bracketItem.gcda:Skip
profiling:/MuseScore:Cannot create directory
profiling:/MuseScore/build.release/libmscore/CMakeFiles/libmscore.dir/stafftypechange.gcda:Skip
profiling:/MuseScore:Cannot create directory
profiling:/MuseScore/build.release/libmscore/CMakeFiles/libmscore.dir/stafftypelist.gcda:Skip
profiling:/MuseScore:Cannot create directory
profiling:/MuseScore/build.release/libmscore/CMakeFiles/libmscore.dir/read300.gcda:Skip
profiling:/MuseScore:Cannot create directory
profiling:/MuseScore/build.release/libmscore/CMakeFiles/libmscore.dir/read206.gcda:Skip
profiling:/MuseScore:Cannot create directory
profiling:/MuseScore/build.release/libmscore/CMakeFiles/libmscore.dir/read114.gcda:Skip
profiling:/MuseScore:Cannot create directory
profiling:/MuseScore/build.release/libmscore/CMakeFiles/libmscore.dir/stafflines.gcda:Skip
profiling:/MuseScore:Cannot create directory
profiling:/MuseScore/build.release/libmscore/CMakeFiles/libmscore.dir/midimapping.gcda:Skip
profiling:/MuseScore:Cannot create directory
profiling:/MuseScore/build.release/libmscore/CMakeFiles/libmscore.dir/systemdivider.gcda:Skip
profiling:/MuseScore:Cannot create directory
profiling:/MuseScore/build.release/libmscore/CMakeFiles/libmscore.dir/shape.gcda:Skip
profiling:/MuseScore:Cannot create directory
profiling:/MuseScore/build.release/libmscore/CMakeFiles/libmscore.dir/scoreElement.gcda:Skip
profiling:/MuseScore:Cannot create directory
profiling:/MuseScore/build.release/libmscore/CMakeFiles/libmscore.dir/keylist.gcda:Skip
profiling:/MuseScore:Cannot create directory
profiling:/MuseScore/build.release/libmscore/CMakeFiles/libmscore.dir/ambitus.gcda:Skip
profiling:/MuseScore:Cannot create directory
profiling:/MuseScore/build.release/libmscore/CMakeFiles/libmscore.dir/bagpembell.gcda:Skip
profiling:/MuseScore:Cannot create directory
profiling:/MuseScore/build.release/libmscore/CMakeFiles/libmscore.dir/spannermap.gcda:Skip
profiling:/MuseScore:Cannot create directory
profiling:/MuseScore/build.release/libmscore/CMakeFiles/libmscore.dir/noteline.gcda:Skip
profiling:/MuseScore:Cannot create directory
profiling:/MuseScore/build.release/libmscore/CMakeFiles/libmscore.dir/mscoreview.gcda:Skip
profiling:/MuseScore:Cannot create directory
profiling:/MuseScore/build.release/libmscore/CMakeFiles/libmscore.dir/groups.gcda:Skip
profiling:/MuseScore:Cannot create directory
profiling:/MuseScore/build.release/libmscore/CMakeFiles
and some more. Seems to be some debug information
Comments
Can confirm with f59ca31. The messages don't appear for example with one of the former versions 2210363.
Note: the messages appear with the nightly of 3.0, not with the last nightly of 2.2 (a09f8e2).
Culprit got to be https://github.com/musescore/MuseScore/pull/3358, fe3e087
In reply to Culprit got to be https:/… by Jojo-Schmitz
Definitely the culprit... No idea why though. The app image is supposed to be built in Release mode and the coverage only on when in Debug and the option is ON (both should be false...) I will have a second look tomorrow morning.
In reply to Definitely the culprit... No… by [DELETED] 5
IIRC I left a comment to the Primary regarding Debug being case sensitive at the place where it got used
In reply to IIRC I left a comment to the… by Jojo-Schmitz
Yes, saw it. Still it's a AND ... I don't get it yet. I tried to make sure the variable is a boolean but it doesn't work I believe. https://github.com/musescore/MuseScore/commit/137a7192595d363f59dae591f…
I will have to get a working linux I guess....
In reply to Yes, saw it. Still it's a… by [DELETED] 5
Case sensitivity is probably irrelevant here anyway, that "Debug" vs. "DEBUG" was mainly needed to suit the defaults of QtCreator, the links build uses "DEBUG" I believe, so we should be in the clear there
In reply to Case sensitivity is probably… by Jojo-Schmitz
Problem has disappearded with 35899c0