Debug Netlinx

DHawthorne wrote:

There is nothing wrong with that code snippet. It's more likely what comes directly after, or something with the nDEBUG value.

Unfortunately, you can't pass a variable to a function by value. The best you can do is duplicate it inside the function by making a variable of the same type, then assigning the parameter value to that, and working with that one instead of the actual parameter.

The debugger keep on stoping all the time even that there is no breakpoint....

DHawthorne wrote:

Yes, but being as this is the last line of code that passes without the debugger stopping, it stands to reason that this code is OK ... it what comes next that stalls it, and it stalls it badly enough that it never acknowledges it was even running.

This is a common issue, by the way, with how NetLinx Studio inserts debug tokens. Even on compile errors, you often get a bad line reported as being a line, or several lines, in front of the actual problem.

Ok

here is the full code

DATA_EVENT[vdvDEVICE]
{
COMMAND:
{
STACK_VAR CHAR datum[30]
STACK_VAR CHAR cCOMMAND[20][20]


IF (nDEBUG > 2)
SEND_STRING dvdDebug, "'UI/Virtual Device 1 received from Comm: ',data.text"
datum = remove_string(data.text, '-', 1)


SWITCH(datum) {
CASE 'TITLECOUNTER-':
{
m_DVDMode = 1
//SEND_COMMAND dvTPList, "'@TXT',nTXT_BTN[1],DATA.TEXT"
SEND_STRING dvdDebug,"'dvd CMD TITLECOUNTER'"
SEND_STRING dvdDebug,DATA.TEXT
m_TITLECOUNTER = DATA.TEXT
}
CASE 'TITLEINFO-':
{
fnPARSE(',',DATA.TEXT,cCOMMAND)
IF(cCOMMAND[1] == '-2147483648')
{
//SEND_COMMAND dvTPList, "'@TXT',nTXT_BTN[2],'TITLE: --'"//TITLE
m_TITLEINFO = "'TITLE: --'"
}
ELSE
{
//SEND_COMMAND dvTPList, "'@TXT',nTXT_BTN[2],'TITLE: ',cCOMMAND[1]"//TITLE
m_TITLEINFO = "'TITLE: ',cCOMMAND[1]"
}
SEND_STRING dvdDebug,"'dvd CMD TITLEINFO'"
SEND_STRING dvdDebug,cCOMMAND[1]
SEND_STRING dvdDebug,m_TITLEINFO

}
CASE 'TRACKCOUNTER-':
{
m_DVDMode = 0
SEND_COMMAND dvTPList, "'@TXT',nTXT_BTN[1],DATA.TEXT"
SEND_STRING dvdDebug,"'dvd CMD TRACKCOUNTER'"
SEND_STRING dvdDebug,DATA.TEXT
m_TRACKCOUNTER = DATA.TEXT
}
CASE 'TRACKINFO-':
{
SEND_COMMAND dvTPList, "'@TXT',nTXT_BTN[3],DATA.TEXT"
fnPARSE(',',DATA.TEXT, cCOMMAND)
IF(cCOMMAND[1] == '-2147483648')
{
//SEND_COMMAND dvTPList, "'@TXT',nTXT_BTN[3],'CHP/TRK: -- '"//CHAPTER
m_TRACKINFO = "'CHP/TRK: -- '"
}
ELSE
{
//SEND_COMMAND dvTPList, "'@TXT',nTXT_BTN[3],'CHP/TRK: ',cCOMMAND[1]"//CHAPTER
m_TRACKINFO = "'CHP/TRK: ',cCOMMAND[1]"
}

SEND_STRING dvdDebug,"'dvd CMD TRACKINFO'"
SEND_STRING dvdDebug,cCOMMAND[1]
SEND_STRING dvdDebug,m_TRACKINFO
}
CASE 'VERSION-':
{
sVERSION = DATA.TEXT
}
CASE 'DEBUG-': {
nDebug = atoi(data.text)
IF (nDebug)
SEND_STRING 0, "'Debug messages are now on.'"
ELSE
SEND_STRING 0, "'Debug messages are now off.'"
BREAK
}
}
}
STRING:
{
SEND_STRING dvdDebug,"'dvd STRING'"
SEND_STRING dvdDebug, DATA.TEXT


}
ONLINE:
{
SEND_COMMAND vdvDEVICE, "'TRACKCOUNTERNOTIFY-1'"
SEND_COMMAND vdvDEVICE, "'TITLECOUNTERNOTIFY-1'"
}
}

I don't understand why it stops here without me putting any break point, and without any code that generate "code break point"

If I want to debug any code in my system, I must remark this code.
its very annoying...

Thanks Dave!

The local_var solved it.


Thanks a lot

Ady