From: Hui Zhu <teawater@gmail.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb@sourceware.org
Subject: Re: [BUG] gdb crash when "python import gtk"
Date: Thu, 19 Jul 2012 07:54:00 -0000 [thread overview]
Message-ID: <CANFwon3w3PuSKgcQEngCC-QZTmUqpeKNfcqirrqzEvz8korXpA@mail.gmail.com> (raw)
In-Reply-To: <20120719073959.GA10044@host2.jankratochvil.net>
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
next prev parent reply other threads:[~2012-07-19 7:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-19 5:26 Hui Zhu
2012-07-19 7:16 ` Hui Zhu
2012-07-19 7:21 ` Phil Muldoon
2012-07-19 7:40 ` Jan Kratochvil
2012-07-19 7:54 ` Hui Zhu [this message]
[not found] ` <A681786A-58A1-41E6-8410-8EBD8330E6BE@cs.umd.edu>
2012-08-30 16:05 ` Disable -lmcheck when Python has threads (Re: [BUG] gdb crash when "python import gtk") Jan Kratochvil
2012-08-30 16:07 ` Jan Kratochvil
2012-08-30 16:09 ` Khoo Yit Phang
2012-08-30 16:11 ` Khoo Yit Phang
2012-08-30 16:41 ` Khoo Yit Phang
2012-09-06 19:30 ` Tom Tromey
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CANFwon3w3PuSKgcQEngCC-QZTmUqpeKNfcqirrqzEvz8korXpA@mail.gmail.com \
--to=teawater@gmail.com \
--cc=gdb@sourceware.org \
--cc=jan.kratochvil@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).