FreeRTOS: hints always report missing queue info, even when info is found and displayed

[malsyned]

In testing out the new FreeRTOS queue support from @hwmland's PR #45, I found that even after successfully configuring the queue registry and adding queues to the registry, I still got a hint reading

Missing Queue/Mutex/Semaphore info..:
Register queues/semaphores/mutexes of interest using vQueueAddToRegistry()

This looks to me like it's because RTOSFreeRTOS.createHmlHelp() is idempotent: it only changes this.helpHtml the first time it's called, which is in the first call to getThreadInfo() from refresh(). That happens before getQueueInfo() is ever called, so this.queueInfo hasn't been populated and will always be [].

This isn't completely trivial to fix, because createHtmlHelp() uses an RTOSStrToValueMap that's local to getThreadInfo(). I think it is fixable, but it'll require a more extensive reworking of how the help text is created and when it is updated.

[haneefdm]

@hwmland Do you have some time to take a look?

[hwmland]

Sorry, not now. Due to workload I still didn't manage even to reinstall RpiPico toolchain yet after my disk crash :(
Isn't it enough to comment one line (see comment in this code fragment):

    protected createHmlHelp(th: RTOSCommon.RTOSThreadInfo, thInfo: RTOSCommon.RTOSStrToValueMap) {
        function strong(s: string) {
            return `<strong>${s}</strong>`;
        }
        if (this.helpHtml === undefined) { // isn't it enough to comment this line out?
            this.helpHtml = '';
            try {
                let ret = '';
                if (!thInfo['uxTCBNumber'].val) {
// code continues here...

[haneefdm]

No, we don't want to do that. Performance is critical and it is super slow as is. It affects single stepping

I will look for an alternate way.

[haneefdm]

It is also not super important for the help to be super context sensitive. It depends on the wording of the Help text.