• Locked Locked
  • Replies 4 replies
  • Subscribers 119 subscribers
  • Views 4235 views
  • Users 0 members are here
Options
Related
How was your experience today?
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

unexpected segmentation fault changing pc register with branch

Davide Quarta
Parents
  • Arm Employee Badge
    Note: This was originally posted on 15th May 2013 at http://forums.arm.com

    I'm not a GDB expert, but can you get it show you the IFSR and IFAR values?  These are the Instruction Fault Status and Instruction Fault Address registers respectively.  They are how the processor reports why instruction fetch failed (which is what I'm guessing is happening).  Couple of possibilities....

    * The memory just isn't mapped (seems unlikely as you've just mapped it, but it's possible you made a mistake)
    * The mapped region is marked as eXecute Never (XN), meaning any attempt to execute the address will fail
    * Access flag (AF bit) in the descriptor has not been set by the kernel yet.
Reply
  • Arm Employee Badge
    Note: This was originally posted on 15th May 2013 at http://forums.arm.com

    I'm not a GDB expert, but can you get it show you the IFSR and IFAR values?  These are the Instruction Fault Status and Instruction Fault Address registers respectively.  They are how the processor reports why instruction fetch failed (which is what I'm guessing is happening).  Couple of possibilities....

    * The memory just isn't mapped (seems unlikely as you've just mapped it, but it's possible you made a mistake)
    * The mapped region is marked as eXecute Never (XN), meaning any attempt to execute the address will fail
    * Access flag (AF bit) in the descriptor has not been set by the kernel yet.
Children
No data