Memory Window Terminates Debug

Sysprogs forums › Forums › VisualGDB › Memory Window Terminates Debug

Log In Register Lost Password
Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • July 27, 2016 at 12:23 #8707
    chris@rflogic.co.uk
    Participant

    I’m trying to debug an externally built project using Quick Visual GDB debug in VStudio 2015. Normal stepping, watch windows , disassembly all work fine. However as soon as I open a memory window the debug session terminates. Looking at the GDB Server console it looks like the memory window is requesting memory reads from  before the requested address, ie memory window address 0x00000000, requests memory reads from 0xffffff3c, which is an illegal address. Is there anyway of stopping this?

    Thanks Chris

    July 27, 2016 at 18:09 #8712
    support
    Keymaster

    Hi,

    This is a known issue. Please try using VisualGDB 5.2 Preview 1. It contains an improved memory window that fixes this issue among other improvements.

    July 27, 2016 at 19:23 #8717
    chris@rflogic.co.uk
    Participant

    Thanks, works a treat. New memory window looks good.

    Now I just need to get Live Watch and Live View working

    July 28, 2016 at 05:05 #8718
    support
    Keymaster

    Hi,

    The live watch/memory should work with OpenOCD and Segger J-Link. If you encounter any problems, feel free to let us know and we will help you solve them.

  • Author
    Posts
Log In Register Lost Password
Viewing 4 posts - 1 through 4 (of 4 total)
  • You must be logged in to reply to this topic.