https://bugs.kde.org/show_bug.cgi?id=514151
--- Comment #1 from Friedrich W. H. Kossebau <[email protected]> --- Hi Brendon Higgins, thanks for the report and interest. Myself, while not being Alexander, the original developer of the Structures tool, I am the one currently now trying to keep the Structures tool alive and to bring it into a Qt6 future. Not a full expert on the code yet, but getting there, and now looking into using the bug report/feature request to enhance some more. After a check on the code, I can imagine that at least for the non-complex arrays keeping the full original array length as separate data clue and using that when calculating the bits size() of the array might get the desired effect to have a proper offset for the things behind the array. Sketched your scenario by the following structure definition: --- 8< --- bug65535.osd <?xml version="1.0" encoding="UTF-8"?> <data> <struct name="Bug 65535"> <array name="zeros" length="100000"> <primitive name="data" type="UInt8" /> </array> <primitive name="enddata" type="UInt32"/> </struct> </data> --- 8< --- --- 8< --- bug65535.desktop [Desktop Entry] Icon=text/plain Type=Service ServiceTypes=KPluginInfo Name=Bug 65535 Comment= X-KDE-PluginInfo-Name=bug65535 X-KDE-PluginInfo-Category=structure --- 8< --- Just, for some yet to explore reason I hit some "Out of memory" exception right now with that OSD. While I wait for the next time slot to continue my investigation, could you please share your OSD file you used, if possible, so I can compare? Any crashes you experienced while experimenting around your large data structure description? -- You are receiving this mail because: You are watching all bug changes.
