# Problems after updating to traceviewer 4.11.1

**URL:** <https://forums.freertos.org/t/problems-after-updating-to-traceviewer-4-11-1/24849>\
**Category:** Percepio\
**Created:** [January 24, 2026, 2:11pm UTC](https://forums.freertos.org/t/problems-after-updating-to-traceviewer-4-11-1/24849 "2026-01-24T14:11:22Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![MartinB](https://avatars.discourse-cdn.com/v4/letter/m/aeb1de/32.png) [@MartinB](https://forums.freertos.org/u/MartinB)\
**Post date:** [January 24, 2026, 2:11pm UTC](https://forums.freertos.org/t/problems-after-updating-to-traceviewer-4-11-1/24849/1 "2026-01-24T14:11:23Z")

</div>

Hi

After updating to 4.11.1, im facing a few problems.

- my \_\_\_stack\_chk\_fail function gets called as xTraceEventCreate1 is returned.
- in trcTaskMonitor.c, there is an assumption that standard stdio.h can always used. It looks like it is prepared that TRC\_CFG\_PRINTF should be a standard configuration define, but it is not mentioned in any other file. I caught this as I have poisoned “malloc” and printf references malloc via reent.h
- In trcKernelPort.h, there are a lot of macros that expand to switch statements. All of these switch statements lack default cases which triggers warnings when compiling with -Wswitch-default

The last two bullets are simply feedback to @johankraft, however I would appreciate help on the stack issue.

I have started to investigate the stack issue, but so far, all things I have done to influence the issue have had no effect.

- I have tested on both GCC 13.3 and 14.3.
- I have tried both -Os and -Og.
- drastically changing \_Min\_Stack\_Size in my .ld file.
- I also tried to increase the idle task stack, knowing that it should not have any effect.

I am working via stm32CubeIDE 2.0 on a stm32G474RE. FreeRTOS version is 11.2.0.

After 37 FreeRTOS tics, this happens

 ![image](https://d2v6vdsk2p900z.cloudfront.net/original/2X/9/938fb76bf7871fdbe3a089f66281f10aecd13b2f.png)

Does anyone have any good ideas?

Best regards,

Martin

---

<div class="post-metadata">

**Author:** ![johankraft](https://avatars.discourse-cdn.com/v4/letter/j/e68b1a/32.png) [@johankraft](https://forums.freertos.org/u/johankraft)\
**Post date:** [January 25, 2026, 7:57am UTC](https://forums.freertos.org/t/problems-after-updating-to-traceviewer-4-11-1/24849/2 "2026-01-25T07:57:08Z")

</div>

Thanks for the feedback. We will investigate this.

So it worked as expected with an earlier version? What version did you use then?

---

<div class="post-metadata">

**Author:** ![MartinB](https://avatars.discourse-cdn.com/v4/letter/m/aeb1de/32.png) [@MartinB](https://forums.freertos.org/u/MartinB)\
**Post date:** [January 25, 2026, 10:23am UTC](https://forums.freertos.org/t/problems-after-updating-to-traceviewer-4-11-1/24849/3 "2026-01-25T10:23:57Z")

</div>

Hi

I have basically done no change since my unorthodox integration of version 4.10.3 that you might remember from this thread

> [@TRACE\_ASSERT upon taking a MUX](https://forums.freertos.org/t/trace-assert-upon-taking-a-mux/23367):
>
> Hi First of all, i apologize if this is not the right forum, but i fail to fund any other supportforum for Percepio view on Percepios own website. I have a system running FreeRTOS 11.2.1 and Trace recorder 4.10.3 in snapshot mode on a STM32G474. I have just started using Percepios tools, so it seems very likely that I am doing something simple wrong. I followed the “getting started” video from Percepio and I also changed a few more config flags. I added assert (TRC\_CFG\_USE\_TRACE\_ASSERT) I u…

since it was so unorthodox, I removed that integration completely and installed a new one.

// Martin

---

<div class="post-metadata">

**Author:** ![MartinB](https://avatars.discourse-cdn.com/v4/letter/m/aeb1de/32.png) [@MartinB](https://forums.freertos.org/u/MartinB)\
**Post date:** [January 25, 2026, 6:11pm UTC](https://forums.freertos.org/t/problems-after-updating-to-traceviewer-4-11-1/24849/4 "2026-01-25T18:11:46Z")

</div>

Hi

The problem is somehow connected to the use of \_\_stack\_chk\_fail.

If I comment out the definition of the \_\_stack\_chk\_guard variable, the problem disappears.

If I remove the -fstack-check-all compiler flag, the problem is instead turned into a Hardfault (Bus, memory management or usage fault, Attempt to switch into invalid state). It is also the detected at another place

 ![image](https://d2v6vdsk2p900z.cloudfront.net/original/2X/5/5ddeb0e30612db7b5e72bea2efc2db45a6d218e9.png)

To be continued.

// Martin

---

<div class="post-metadata">

**Author:** ![Boudewijn.Dijkstra](https://avatars.discourse-cdn.com/v4/letter/b/3ec8ea/32.png) [@Boudewijn.Dijkstra](https://forums.freertos.org/u/Boudewijn.Dijkstra)\
**Post date:** [January 26, 2026, 10:40am UTC](https://forums.freertos.org/t/problems-after-updating-to-traceviewer-4-11-1/24849/5 "2026-01-26T10:40:06Z")

</div>

Hi Martin,

It looks like you’re simply running out of stack space. If you investigate the HardFault, you will probably find a value in BFAR that’s just outside of a stack. When a SysTick IRQ happens, which stack is used? Are you sure that you tried to increase this stack?

Best regards,  
Boudewijn (FAE at Percepio)

---

<div class="post-metadata">

**Author:** ![MartinB](https://avatars.discourse-cdn.com/v4/letter/m/aeb1de/32.png) [@MartinB](https://forums.freertos.org/u/MartinB)\
**Post date:** [January 26, 2026, 11:12am UTC](https://forums.freertos.org/t/problems-after-updating-to-traceviewer-4-11-1/24849/6 "2026-01-26T11:12:22Z")

</div>

Thanks for the feedback

I will double check this tonight.

// Martin

---

<div class="post-metadata">

**Author:** ![MartinB](https://avatars.discourse-cdn.com/v4/letter/m/aeb1de/32.png) [@MartinB](https://forums.freertos.org/u/MartinB)\
**Post date:** [January 26, 2026, 10:44pm UTC](https://forums.freertos.org/t/problems-after-updating-to-traceviewer-4-11-1/24849/7 "2026-01-26T22:44:17Z")

</div>

Hi Boudewijn

BFAR is `0xE000EDF8` (close to the actual address of BFAR interestingly 🙂 )

I should mention that I force busfaults to be precise by issuing:

`SCnSCB->ACTLR = (SCnSCB->ACTLR | SCnSCB_ACTLR_DISDEFWBUF_Msk);`

I showed in the original post that the Systick was called when the IDLE task was running. Here is a different view showing the same thing

 ![image](https://d2v6vdsk2p900z.cloudfront.net/original/2X/4/4b6b424c03cdaa647d821d9cb36a4eb01daf7258.png)

But you are right. The problem is indeed a blown stack. I had a too aggressively big heap area which obviously gave me a (too) small stack. The reason why I did not catch that seems to be that I have done something wrong with the stack canaries that does not seem to trigger in the way that it should.

Thanks so much for the assistance.

I will keep adding to this thread when i figure out why that is.

But for now it works. I am abit confused about some of the output as View does not seem to pick up all the task names.

 ![image](https://d2v6vdsk2p900z.cloudfront.net/original/2X/6/61c1ec57441ab761f67c111ab2f4f95fb7db29b0.png)

Best regards

Martin

---

<div class="post-metadata">

**Author:** ![Boudewijn.Dijkstra](https://avatars.discourse-cdn.com/v4/letter/b/3ec8ea/32.png) [@Boudewijn.Dijkstra](https://forums.freertos.org/u/Boudewijn.Dijkstra)\
**Post date:** [January 27, 2026, 10:34am UTC](https://forums.freertos.org/t/problems-after-updating-to-traceviewer-4-11-1/24849/8 "2026-01-27T10:34:30Z")

</div>

Hi Martin,

Good to hear that it works now. I can’t explain the BFAR value.

We have a blog page about object names:

> **[Naming your kernel objects - Percepio](https://percepio.com/naming-your-kernel-objects/)**
>
> When using Percepio Tracealyzer and TraceRecorder, you may have noticed that thread names show up automatically, while other kernel objects (like queues or semaphores) are only displayed as hexadecimal numbers. But in the demo traces, all kernel...

The _Troubleshooting_ section should help you.

/Boudewijn

---

<div class="post-metadata">

**Author:** ![MartinB](https://avatars.discourse-cdn.com/v4/letter/m/aeb1de/32.png) [@MartinB](https://forums.freertos.org/u/MartinB)\
**Post date:** [January 28, 2026, 11:48am UTC](https://forums.freertos.org/t/problems-after-updating-to-traceviewer-4-11-1/24849/9 "2026-01-28T11:48:09Z")

</div>

Hi and thanks for the link. I will investigate it.

Regarding the switch-default warnings, my own sollution was to add this to trcKernelPort.h

```auto
#define traceADD_SWITCH_DEFAULT() \
		default: \
			break;

```

And then add calls to that to all macros that lacked the ending default case like this for example.

```auto
#define traceQUEUE_CREATE( pxNewQueue )\
	switch ((pxNewQueue)->ucQueueType) \
	{ \
		case queueQUEUE_TYPE_BASE: \
		traceQUEUE_SET_CASE_HELPER() \
			(void)xTraceObjectRegisterWithoutHandle(PSF_EVENT_QUEUE_CREATE, (void*)(pxNewQueue), "", (uint32_t)uxQueueLength); \
			break; \
		case queueQUEUE_TYPE_BINARY_SEMAPHORE: \
			(void)xTraceObjectRegisterWithoutHandle(PSF_EVENT_SEMAPHORE_BINARY_CREATE, (void*)(pxNewQueue), "", 0); \
			break; \
		traceQUEUE_CREATE_HELPER() \
		traceADD_SWITCH_DEFAULT() \
	}

```

Regards

Martin
