mcu-debug / rtos-views

RTOS views for microcontrollers
MIT License
24 stars 11 forks source link

How can i view my task name? #42

Open USTHzhanglu opened 6 months ago

USTHzhanglu commented 6 months ago

image I used freeRTOS in my mcu, the Task Name just show address, i don't now how to view it. if somebody know,please help me,thanks

USTHzhanglu commented 6 months ago

by debug, i get this message tmpThName:"0x2000090c <ucHeap+1080> <error reading variable>"

USTHzhanglu commented 6 months ago

image and i can read str by MemoryView like this.

This is some log in rtos-debug

const result = await this.session.customRequest(cmd, arg);
/**
cmd is `evaluate`
arg is 
{
  frameId: 4096,
  expression: "(char *)((TCB_t*)0x200008d8).pcTaskName",
  context: "hover",
}

resault is

{
  result: "0x2000090c <ucHeap+1080> <error reading variable>",
  type: "char *",
  presentationHint: {
  },
  variablesReference: 3145788,
  memoryReference: "0x2000090c",
}

**/

hope this log helpful

PhilippHaefele commented 6 months ago

Hi @USTHzhanglu Can you please state your system versions like VSCode, extension and most important FreeRTOS.

Without these we're not able to help you at all

USTHzhanglu commented 6 months ago

Hi @USTHzhanglu Can you please state your system versions like VSCode, extension and most important FreeRTOS.

Without these we're not able to help you at all

OS: Windows 11 22H2 Vscode: 1.85.1 extension : 0.0.7 freeRTOS: FreeRTOSv202112.00 probe: stlink debuger: openocd 0.12.0-rc2-g7a1adfbec (2022-11-06-10:08)

htcrane commented 2 months ago

I am facing a similar issue as well: only the first character of a task name will appear in the XRTOS table. When I use char* test = pcTaskGetName(NULL); to get the task name address, it appears as the full name with null termination in memory view.

OS: MacOS 14.4.1 Vscode: 1.88.0 Extension: 0.0.7 Cortex Debug Version: 1.12.1 FreeRTOS: 10.5.1 Probe: JLINK-EDU Debugger: arm-none-eabi tool chain v13.2.1Rel1

thirtytwobits commented 1 week ago

Been seeing this for months now so it probably showed up in an earlier vscode revision. Used to work with the same version of FreeRTOS under test:

Mac OS: 14.5 (M2) vscode: 1.90.2 mcu-debug RTOS Views: 0.0.7 FreeRTOS: 10.4.6 Probe: Jtrace Debugger: gdb from 10.3