Hey, yami wrote: > I know that Purify can show the problematic source code too. Is it > possible to show the corresponding code snippet reported by Purify ? >
I wasn't able to extract the offending file/line out of Purify because it didn't show any. I think I know what is going on. Note that when we build on Windows, we use set of optimized functions in asm_utils_win32_x86.asm instead of asm_utils.c. AFAICT the implementation in asm_utils_win32_x86.asm reads 4 bytes at a time which could explain the uninitialized memory reads I was seing. -- Best Regards, Kobi ___________________________________________________________________________ Sent via: Wireshark-dev mailing list <[email protected]> Archives: http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:[email protected]?subject=unsubscribe
