View Single Post
  #1   Spotlight this post!  
Unread 10-02-2014, 14:21
wireties's Avatar
wireties wireties is offline
Principal Engineer
AKA: Keith Buchanan
FRC #1296 (Full Metal Jackets)
Team Role: Mentor
 
Join Date: Jan 2006
Rookie Year: 2004
Location: Rockwall, TX
Posts: 1,170
wireties has a reputation beyond reputewireties has a reputation beyond reputewireties has a reputation beyond reputewireties has a reputation beyond reputewireties has a reputation beyond reputewireties has a reputation beyond reputewireties has a reputation beyond reputewireties has a reputation beyond reputewireties has a reputation beyond reputewireties has a reputation beyond reputewireties has a reputation beyond repute
Send a message via AIM to wireties
Re: WindRiver Debug Mode question

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
__________________
Fast, cheap or working - pick any two!
Reply With Quote