Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

VxWorks: For when it can't crash...ever. Some of the most entertaining and enlightening projects I have ever worked on were centered around VxWorks.

Interesting interview. I liked the bit at the end about not allowing dynamically allocated memory!



Regarding crashing:

  Am I right in assuming that there's very little process separation in the older RAD 6000 boards?  

  There is no process separation. I mean basically what we — 
 
  One bad pointer in one module and —  

  Exactly.  — 

  you wait for the next update window.  

  Exactly.  

  Wow. I could write software like that.  
  
  [Laughs] Well —  

  I won't give you a 90 percent certainty though.  

  We have strict coding guidelines that we use. We don't allow dynamic memory allocation, for example.


You can still suffer priority inversion under VxWorks (indeed, this has happened to NASA).




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: