It doesn't crash anymore with new pre-release...(0.10.13)
It is working slower while allocating memory and allocates 40% less
memory for a capture file which contains 100k packets during exporting
pdml output, but the good news it never crashes...
Thanks,
Ceyhun
-----Original Message-----
From: ethereal-dev-bounces@xxxxxxxxxxxx
[mailto:ethereal-dev-bounces@xxxxxxxxxxxx] On Behalf Of Seran, Ceyhun
[CTF:2370:EXCH]
Sent: vendredi 14 octobre 2005 10:59
To: Ethereal development
Subject: RE: [Ethereal-dev] G_malloc vs malloc
Hi again,
I am also curious after the replies...We observe this behaviour in
windows 2k 5.00.2195 service pack 4 and windows server 2003 standard
edition service pack 1.
I am still insistent about this problem. Used and free'd memory cause
problems in actual version by g_malloc usage in windows environment.
You can check with these files and see the behaviour. (The capture file
was containing 100k packets, originally... In onl.cap ( cut into 0-1500
packets) in onl2.cap (0 to 625 packets). In latest release, the first
file crashes after 100st packet, in the second file which contains the
"same packets" it crashes, instantly...
http://rapidshare.de/files/6260930/onl.cap.html
Or
http://rapidshare.de/files/6260960/onl2.cap.html
To reproduce the problem in windows environment:
-Load one of the capture files using latest or any release of ethereal,
try to export as pdml file. It will crash somewhere...
I you uninstall and reinstall ethereal using this modified and version
of the ethereal (g_malloc() replaced by malloc() and g_malloc0() by
calloc() ), it never crashes...
http://rapidshare.de/files/6261005/ethereal-setup-0.10.12-v2.exe.html
I attach also the svn diff file (changes in the source code)
http://rapidshare.de/files/6261203/corrections.txt.html
P.S. = to download the files click to free option in the page and wait
about 20 seconds for the activation of the download link...
Regards,
Ceyhun
-----Original Message-----
From: ethereal-dev-bounces@xxxxxxxxxxxx
[mailto:ethereal-dev-bounces@xxxxxxxxxxxx] On Behalf Of Jaap Keuter
Sent: jeudi 13 octobre 2005 18:29
To: Ethereal development
Subject: Re: [Ethereal-dev] G_malloc vs malloc
On Thu, 13 Oct 2005, Ceyhun Seran wrote:
> Hi,
>
> To avoid usage of g_malloc() which results crashes in ethereal, I ...
> By replacing g_malloc() by malloc(), when the used memory is returned
to
> system by free(), the memory can be reallocated by another malloc()
call
> which doesn't crash ethereal...
Now we are curious on what platform you see this behaviour...?
_______________________________________________
Ethereal-dev mailing list
Ethereal-dev@xxxxxxxxxxxx
http://www.ethereal.com/mailman/listinfo/ethereal-dev
_______________________________________________
Ethereal-dev mailing list
Ethereal-dev@xxxxxxxxxxxx
http://www.ethereal.com/mailman/listinfo/ethereal-dev
