On Wed, Mar 14, 2012 at 09:01:07PM +0100, Akos Vandra wrote: > 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.
In which way? It should return NULL (glib-like) or some not-NULL pointer (glibc-like)? AFAIR in C standard it's UB. But the problem is that you are probably writting to *ep_alloc(0), please check. Cheers, Jakub. ___________________________________________________________________________ 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
