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

[Hui Zhu <teawater at gmail dot com>]

Hi Jan,

Without http://sourceware.org/git/?p=gdb.git;a=commit;h=d43ca3bfc165c72be20288233d20d61ec107a2de
that you committed.

This issue doesn't occur.

Thanks,
Hui

On Thu, Jul 19, 2012 at 1:25 PM, Hui Zhu <teawater@gmail.com> wrote:
> GNU gdb (GDB) 7.5.50.20120719-cvs
> Copyright (C) 2012 Free Software Foundation, Inc.
> License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
> This is free software: you are free to change and redistribute it.
> There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
> and "show warranty" for details.
> This GDB was configured as "x86_64-unknown-linux-gnu".
> For bug reporting instructions, please see:
> <http://www.gnu.org/software/gdb/bugs/>.
> (gdb) python import gtk
> memory clobbered before allocated block
> Aborted (core dumped)
>
> But in 7.4.1 is OK.
> ./gdb
> GNU gdb (GDB) 7.4.1.20120718-cvs
> Copyright (C) 2012 Free Software Foundation, Inc.
> License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
> This is free software: you are free to change and redistribute it.
> There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
> and "show warranty" for details.
> This GDB was configured as "x86_64-unknown-linux-gnu".
> For bug reporting instructions, please see:
> <http://www.gnu.org/software/gdb/bugs/>.
> Setting up the environment for debugging gdb.
> No symbol table is loaded.  Use the "file" command.
> Make breakpoint pending on future shared library load? (y or [n])
> [answered N; input not from terminal]
> No symbol table is loaded.  Use the "file" command.
> Make breakpoint pending on future shared library load? (y or [n])
> [answered N; input not from terminal]
> .gdbinit:8: Error in sourced command file:
> Argument required (one or more breakpoint numbers).
> (gdb) python import gtk
>
>
> I will spend some time on it but I am not sure I can fix it.
> 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.
>
> Thanks,
> Hui