Undefined reference errors when trying to build with the Instrumenting Profiler

[Jose Cazarin]

Hello, when I add the call to InitializeInstrumentingProfiler() in the main loop I get the following errors in the linking step:
<pre style=”text-align: left;”>C:/Users/user/AppData/Local/VisualGDB/EmbeddedEFPs/Profiler/InstrumentingProfiler.cpp:117: undefined reference to `SysprogsInstrumentingProfiler_QueryAndResetPerformanceCounter’
Debug_Tag/InstrumentingProfiler.o: In function `SysprogsInstrumentingProfiler::Chronometer::ProfilerTimeRegionRAII::~ProfilerTimeRegionRAII()’:
C:/Users/user/AppData/Local/VisualGDB/EmbeddedEFPs/Profiler/InstrumentingProfiler.cpp:126: undefined reference to `SysprogsInstrumentingProfiler_QueryAndResetPerformanceCounter’
C:/Users/user/AppData/Local/VisualGDB/EmbeddedEFPs/Profiler/InstrumentingProfiler.cpp:126: undefined reference to `SysprogsInstrumentingProfiler_QueryAndResetPerformanceCounter’
Debug_Tag/InstrumentingProfiler.o: In function `InstrumentingProfilerInitialized’:
I am referencing the proper framework as you can see in the attached screenshot. Any suggestions on how to fix that?

• This topic was modified 3 years, 9 months ago by Jose Cazarin.
• This topic was modified 3 years, 9 months ago by Jose Cazarin.

Attachments:

You must be logged in to view attached files.

[support]

Hi,

Normally, the function would be defined in the InstrumentingProfiler.cpp file. Please try locating it in Solution Explorer to see why the function is not properly built.

If you have enable the “use custom performance counter” setting, you would need to provide your own implementation of the function (see this tutorial for details).

[Jose Cazarin]

It wasn’t automatically added to the build, I did it manually (had to go to the C:\Users\user\AppData\Local\VisualGDB\EmbeddedEFPs\Profiler) directory to find the file
I did that, but now I’m getting the same errors but related to other functions, and it’s strange because they are defined in that same file
Shouldn’t the InstrumentingProfiler.cpp be added automatically in the first place when I checked the box to enable the Profiling?

[support]

Normally it should be added automatically. It’s hard to say why it wasn’t, but if you can reproduce the problem reliably and share the steps with us, we will be happy to fix it.

[Jose Cazarin]

So, I’m using version 5.5 preview 5, build 3595
In the attached screenshots, after I click in “Enable relocation record generation” in the step_2 screen, a window pops up and tells me to rebuild the project and then go back to that screen
After I go back to that screen, I can see the screen in the step_3 image
After that, I go to “Analyze performance with visualGDB”, and then I can see the screen on step_4
I select the second option “Instrument functions to record their time”
But when I click “Ok” I see the error on error_1.
That’s when I tried to add the call to InitializeInstrumentingProfiler and then I got my original error

Am I doing it right?

• This reply was modified 3 years, 9 months ago by Jose Cazarin.

Attachments:

You must be logged in to view attached files.

[support]

Thanks, the steps you described should normally work, so most likely the problem is caused by some project-specific setting.

Normally, SysprogsInstrumentingProfiler_QueryAndResetPerformanceCounter would be defined in the InstrumentingProfiler.cpp file inside the profiler framework (unless you are using Nordic nRF5x devices that do not have a DWT register and require a timer-based implementation in ProfilerDriver_Nrf5x.cpp).

Searching all files included in the project for SysprogsInstrumentingProfiler_QueryAndResetPerformanceCounter  should explain why it’s not being linked properly.

[Jose Cazarin]

I’m actually using an NRF5x device, so maybe that’s the problem in the first place?

[support]

Yes, it could be related. Please try manually adding the Nordic-specific driver file (ProfilerDriver_Nrf5x.cpp) to the project.

• This reply was modified 3 years, 9 months ago by support.

[Author]

Posts