Re: [BUG] gdb crash when "python import gtk"

Hui Zhu
2012-07-19T07:54:38Z

On Thu, Jul 19, 2012 at 3:39 PM, Jan Kratochvil
<jan.kratochvil@redhat.com> wrote:
> Hi Hui,
>
> On Thu, 19 Jul 2012 09:15:57 +0200, Hui Zhu wrote:
>> Without http://sourceware.org/git/?p=gdb.git;a=commit;h=d43ca3bfc165c72be20288233d20d61ec107a2de
>> that you committed.
>
> the problem is apparently the new -lmcheck lightweight memory corruption
> testing.
>
>
>> On Thu, Jul 19, 2012 at 1:25 PM, Hui Zhu <teawater@gmail.com> wrote:
>> > GNU gdb (GDB) 7.5.50.20120719-cvs
> [...]
>> > (gdb) python import gtk
>> > memory clobbered before allocated block
>> > Aborted (core dumped)
>
> So the bug is in some gtk code, either the Python binding or the C gtk
> implementation itself.
>
>
>> > But in 7.4.1 is OK.
>
> It did not use -lmcheck so the memory corruption still was there but it was
> not shown.
>
>
>> > I think this issue is dangerous because we don't know how much other
>> > python modules are affected by this issue. Wish it can be fixed
>> > before 7.5 release.
>
> It will not affect the 7.5 release and neither the 7.5 pre-releases:
> [commit/branch] development mode no longer enabled by default
> http://sourceware.org/ml/gdb-patches/2012-07/msg00251.html
>
> On Fedora 17 x86_64 I do not see any problem even with more thorough memory
> testing via valgrind:
> valgrind ./gdb -ex 'python import gtk' -ex q
> pygtk2-2.24.0-4.fc17.x86_64
> gtk2-2.24.10-2.fc17.x86_64
>
> So you should file it as pygtk2 bug for the distro you use.
>
>
> Thanks,
> Jan

OK. Thanks for your help.

Report this issue to
https://bugs.launchpad.net/ubuntu/+source/pygtk/+bug/1026487

Thanks,
Hui