I was referring to the fact that malloc(0) should run fine, without any errors.
Turns out I indeed overlooked something, and really was writing the
pointer returned, so please disregard my report.
Regards,
Ákos
On 14 March 2012 21:51, Guy Harris wrote:
>
> On Mar 14, 2012, at 1:15 PM, Jakub Za
On Mar 14, 2012, at 1:15 PM, Jakub Zawadzki wrote:
> 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 work
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
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
On 3/14/2012 3:52 PM, Akos Vandra 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 b
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 c
