Hi! Figured it out, however this is a bug in wireshark, I suppose. A call to ep_alloc(0) was the culprit. IMHO that should not be a problem, as I expect it to work as malloc works, and malloc should handle a 0 size, as stated in the C standard.
Regards, Ákos On 14 March 2012 20:52, Akos Vandra <axo...@gmail.com> wrote: > Hi! > > I'm developing a dissector for a proprrietary protocol. It has been > working up until now. Today it started crashing wireshark, with the > not very helpful message: > > " > 20:48:51 Err Memory corrupted > Aborted > " > > Can you please help me what could be the problem? I am using ep_alloc > in the code, but it shouldn't be a problem, as it only allocates a few > bytes (<32) > > Regards, > Ákos Vandra ___________________________________________________________________________ Sent via: Wireshark-dev mailing list <wireshark-dev@wireshark.org> Archives: http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
