Bug#178590: libc6: mallopt() segfaults with gpasman
>>>>> "gm" == GOTO Masanori <gotom@debian.or.jp> writes:
gm> I download and build then test it, but no problem.
gm> I guess this bug is caused by memory leak or inappropriate
gm> memory handling of your application. If malloc() has such
gm> major bugs, then you get a lot of application hung :-)
I fully agree. :) The only strange thing is that gpasman worked
flawlessly under glibc2.2, and the bug is triggered inside GTK-1.2.
So I guess it's either a faulty use of GTK by the program, or a faulty
use of malloc()/mallopt() by GTK (where "faulty" means "not standard,
not documented, cornerstone behaviour). I suspect the first.
gm> Yes, please take us the test case.
It's on the TODO list (it's the equivalent of a home-made wormhole).
bye,
andrea
--
Andrea Glorioso andrea.glorioso@binary-only.com
Binary Only http://www.binary-only.com/
Via A. Zanolini, 7/b Tel: +39-348.921.43.79
40126 Bologna Fax: +39-051-930.31.133
Reply to: