Bug#178590: libc6: mallopt() segfaults with gpasman
At Tue, 28 Jan 2003 11:55:57 +0100,
andrea.glorioso@binary-only.com wrote:
> >>>>> "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.
Yes, it may be a gtk problem, from your gdb trace.
> gm> Yes, please take us the test case.
>
> It's on the TODO list (it's the equivalent of a home-made wormhole).
Thanks, I hope you get a clue.
Regards,
-- gotom
Reply to: