On Thu, Apr 27, 2023 at 12:19 AM Dwight Kulkarni <dwi...@realtime-7.com> wrote: > > Your code is exactly what I had before. But I was getting that heap error. It > only went away when I used NEW. I have never seen that before. I also don't > like using NEW at all but it wasn't working. >
When moving an allocation from the stack to the heap (using new), and behavior changes (like no memory error), it indicates a memory error. The problem existed before and after. The heap just masked it. Go back to your original program, and use Address Sanitizer on it. It will show you where the error is, or give you a toe hold into the problem. Jeff -- You received this message because you are subscribed to the Google Groups "Crypto++ Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to cryptopp-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/cryptopp-users/CAH8yC8nQqZCewJuHOWMF30j%3DAvbJ26vuBMjJDyF86nA_%2BjkNbw%40mail.gmail.com.
