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

Debugger unable to view large structs

Hello,

I am using ARM Development Studio for debugging and have encountered some problems with the debugger's handling of large c structs.

EDIT: The following part about size is unrelated to the bug and I misread the numbers (see first Answer to this post).

In the variables view it shows the following for my struct vm

However, the actual size of struct vm is 76256 (I added a print to get sizeof(struct vm)) and I am unable to access fields of the struct that are outside of the size shown in the Variables view.

Even when using the debugger commands to print vms[0].something it fails with ERROR(EXP16): Member "something" not found despite something being a member of the struct.

Is there a way to view larger structs with the ARM Debugger?

I am thankful for any help!

Greetings

Martin.S

Parents
  • Hi Stephen,

    Sorry that I didn't reply earlier. First off, unticking "Use LLVM Dwarf Parser" indeed fixed the bug and now I am able to see all struct members!
    Great to hear that you could reproduce the error and are working on a fix.

    About the size in my original post, I somehow misread the numbers and thought the size shown in ARM DS was smaller than the actual size in bytes.

    I did not encounter members shown as "Optimized Away" (apart from occasions where I assume they acutally were optimized).

    Thanks for your fast help and the workaround.

    Kind Regards

    Martin

Reply
  • Hi Stephen,

    Sorry that I didn't reply earlier. First off, unticking "Use LLVM Dwarf Parser" indeed fixed the bug and now I am able to see all struct members!
    Great to hear that you could reproduce the error and are working on a fix.

    About the size in my original post, I somehow misread the numbers and thought the size shown in ARM DS was smaller than the actual size in bytes.

    I did not encounter members shown as "Optimized Away" (apart from occasions where I assume they acutally were optimized).

    Thanks for your fast help and the workaround.

    Kind Regards

    Martin

Children
No data