WindRiver Debug Mode question

[nollchr]

Wondering if it is normal to need to reboot the CRIO each time after "Terminating" our robot code? During normal debugging, after we terminate our code and recompile, the new code will only run if we reboot the CRIO prior to starting a new debug session. V3.3 of Workbnech.

Thanks in advance.

Chris.

[wireties]

It is "in theory" possible to simply reload your code and run it again. In practice you need to run cleanly (not screw up memory anywhere) and shut the code down cleanly (destroy all your WPI classes etc). Plus VxWorks (the cRIOs operating systems) does not clean up after your code the way a Windoze or Linux process would. VxWorks reaps the task control block and your stacks but nothing else.

In the "real world", my experience is that most people DO reboot the machine before starting a debugging session with new code. In this sort of environment, the code is written to run forever. Most developers do not take the time to make sure their code can be loaded, run, stopped then unloaded cleanly just to support the debugging environment.

HTH

[nollchr]

It is "in theory" possible to simply reload your code and run it again. In practice you need to run cleanly (not screw up memory anywhere) and shut the code down cleanly (destroy all your WPI classes etc). Plus VxWorks (the cRIOs operating systems) does not clean up after your code the way a Windoze or Linux process would. VxWorks reaps the task control block and your stacks but nothing else.

In the "real world", my experience is that most people DO reboot the machine before starting a debugging session with new code. In this sort of environment, the code is written to run forever. Most developers do not take the time to make sure their code can be loaded, run, stopped then unloaded cleanly just to support the debugging environment.

HTH

That is what I figured. Thanks for the response!