Gprof and Gcov don't work

[Andrey Kamenshchikov]

Hello,

I found that Gprof and Gcov profilers don't work for cmake4eclipse-driven projects - see the attached screenshots. is it a misconfiguration - or a bug?

Eclipse CDT: 2024-09 (4.33.0)

cmake4eclipse: 5.0.0

OS: Linux (Debian 12)

Thank you,

Andrey

[Martin Weber]

Am Donnerstag, 26. September 2024, 23:53:18 CEST schrieb Andrey Kamenshchikov:
> Hello,
>
> I found that Gprof and Gcov profilers don't work for cmake4eclipse-driven
> projects - see the attached screenshots. is it a misconfiguration - or a

Most probably a misconfiguration.
Did you create your project as a 'Cmake4eclipse Managed Build'? If not, you
have the plugin installed but are actually not using it.

Cmake4eclipse takes your CMakelists.txt as the source of trouth. Hence you
will have to tell cmake to generate gcov information in the CMakelists.txt

Martin

--
Cd wrttn wtht vwls s mch trsr.

[Andrey Kamenshchikov]

Hello Martin,

Thank you for the comment!

I do set up the project via cmake4eclipse - and drive it with the respective interfaces.

I already tried to set up the gprof flags in the CMakeLists.txt and in the cmake4eclipse (CMake) settings of the project, and I see the flags being propagated to the build in the console - it doesn't change a thing, the errors from the screenshots are still there. Remarkably, gprof and gcov work in other, non cmake4eclipse, projects.

Do they work for you?

Thank you,

Andrey

[Martin Weber]

Am Samstag, 28. September 2024, 21:18:42 CEST schrieb Andrey Kamenshchikov:
> Hello Martin,
>
> Thank you for the comment!
>
> I do set up the project via cmake4eclipse - and drive it with the
> respective interfaces.
>
> I already tried to set up the gprof flags in the CMakeLists.txt and in the
> cmake4eclipse (CMake) settings of the project, and I see the flags being
> propagated to the build in the console - it doesn't change a thing, the
> errors from the screenshots are still there. Remarkably, gprof and gcov
> work in other, non cmake4eclipse, projects.
>
> Do they work for you?

Honestly, I never tried that.