Sysprogs forums › Forums › VisualGDB › Dynamic analysis VisualGDB crash
- This topic has 8 replies, 4 voices, and was last updated 4 years, 5 months ago by support.
-
AuthorPosts
-
September 5, 2019 at 13:16 #25753mmiloParticipant
Whenever I enable “Dynamic Analysis” -> “Real-time watch & trace” -> “Allow tracing various RTOS events in Real-time watch”, VisualGDB crashes with:
“Debugging failed” (see attached screenshot for details)
“taskTaskControlBlock does not contain a member called pcTaskName”I have a “standalone” project on the IMXRT1052. Embedded Frameworks is enabled, and works fine for semihosting. It’s a freeRTOS based project.
Reproduction:
- Create new imxrt10xx project
- import newest SDK
- select any freeRTOS example
- This won’t build as default – so convert to standalone project
- Import all the freertos objects
- add embedded framework
- enable dynamic analysis
Attachments:
You must be logged in to view attached files.September 6, 2019 at 04:56 #25756supportKeymasterHi,
No problem, it looks like VisualGDB doesn’t support the FreeRTOS version you are using, but it should be very easy for us to resolve. Could you please share a link/attach the exact SDK you are using so that we could ensure we are looking at the same thing?
September 6, 2019 at 07:11 #25757mmiloParticipantI’m using the newest SDK: 2.6.1, it contains the FreeRTOS Kernel v10.1.1 (Amazon FreeRTOS). It’s impossible to link to the SDK, you have to generate it and get a personal download from nxp’s website. I’ve attached a cut-down version of the FreeRTOS part of the SDK to make it fit the 0.5MB limit.
Attachments:
You must be logged in to view attached files.September 8, 2019 at 04:40 #25763supportKeymasterNo problem, we have rechecked the latest generated SDK and fixed both the build issue and the field offset detection problem.
Please try this build: VisualGDB-5.5.1.3252.msi
Please note that you would need to re-import the KSDK from the VisualGDB wizard in order to fix the FreeRTOS-related build errors.
July 5, 2020 at 10:12 #28667VladTParticipantthe problem is the same….
I use STM32 and STM32CubeMX
Attachments:
You must be logged in to view attached files.July 5, 2020 at 10:32 #28670VladTParticipantafter installation VisualGDB-5.5.1.3252.msi everything returned to normal…
Is this the latest version? or is there more fresh?
July 5, 2020 at 12:30 #28674supportKeymasterPlease try installing VisualGDB 5.5 Preview 7 from our download page instead. It should include the latest updates.
It the problem persists, please let us know and we will investigate it further.
July 8, 2020 at 06:49 #28709elivoeParticipantHi everyone,
I had exactly the same problem with my Infineon XMC4500. After installing the new Version of VisualGDB the error is replaced by a new one:
VisualGDB version: 5.5.7.3666
—————— System.Exception ——————
System.Exception: Could not find the following symbol in <Project>:
SysprogsRTOSHooks_FreeRTOS_vTaskSwitchContextPlease ensure that your project references the profiler framework, calls the InitializeInstrumentingProfiler() function and is built with the USE_FREERTOS preprocessor macro.
at zg1.h(String d, String e, i c, String b, n a, f f)
at xj..ctor(String c, EmbeddedDynamicAnalysisSettings a, String f, qr g, i h, j d, EmbeddedRTOSProfile b, Dictionary`2 e)
at vs1.i(Boolean a)
at vs1.g_2(DebugCustomizationSettings b, Boolean a)
at o41.p2()
at x8.e2()
at VisualGDB.GDBDebugEngine.w1(rz1 a, m1 b)
trace=[zg1.h:628, xj..ctor:1475, vs1.i:2275, vs1.g_2:24, o41.p2:36, x8.e2:22, VisualGDB.GDBDebugEngine.w1:58]It would be great if you could help me!
Yours,
Elias
July 8, 2020 at 07:49 #28711supportKeymasterNo problem, we can help you.
This error happens when you build a FreeRTOS-based project without referencing the semihosting/profiler framework, or without defining that USE_FREERTOS macro.
If the framework is referenced and the macro is defined, please double-check that the ProfilerFreeRTOSHooks.h file is added to the project as a forced include (referencing the profiler framework should do it manually).
-
AuthorPosts
- You must be logged in to reply to this topic.