title: Can a TLB (Load Word) exception be caused by incorrect compiler options usage?
body: <p>I am getting a TLB (Load Word or Instruction Fetch) exception in VxWorks. When I analyze further I understood that the memory address which is being referred doesn't point to a valid memory location.</p>
  
  <p>As far as I understand, this problem could be happening because of some memory corruption (possible memory overwrite). But, analysis of code and execution of the same piece of code in Windows under purify doesn't show any memory errors.</p>
  
  <p>So, I am wondering if any compiler options could be causing this? Is it possible?</p>
  
  <p>Also, any pointers for how to debug such issues?</p>