NetBurner Community Forum

Hello,

Using NNDK 24 RC2, I am trying NBEclipse for the first time with our legacy application that runs on the SB72.

It is mostly working. I can set breakpoints, trigger breakpoints, and single-step at the source level. Very nice.

The problem is the Eclipse Debug view only indicates three threads (tasks), and our application has fourteen tasks. I can only single-step the source for the three tasks that actually appear.

Netburner TaskScan sees all fourteen tasks.

If I comment out one of the three tasks and rebuild, Eclipse Debug shows different tasks, but is still limited to three.

Do you recognize this symptom? Any suggestions?

Thanks.

Jim

I figured it out.

After posting the question, I recalled a similar issue in Feb 2006 using Netburner GDB/Insight.

From my Feb 2006 notes, the problem then was that the precompiled debug Ethernet driver was built by Netburner with UCOS_STACKCHECK disabled, and using it with an application where UCOS_STACKCHECK is enabled had side-effects including including GDB breakpoint location confusion.

I disabled UCOS_STACKCHECK for our application build just now, and the NBEclipse Debug view shows all of our tasks and I can single-step the source properly. Success.

However, I would like to build our application with UCOS_STACKCHECK enabled. Is the precompiled debug Ethernet driver available for NNDK 24 RC2 built with UCOS_STACKCHECK enabled?

Thanks.

Jim