This is the mail archive of the gdb@sourceware.org mailing list for the GDB project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: GDB crashing because of Python

From: Tom Tromey <tromey at redhat dot com>
To: Kevin Pouget <kevin dot pouget at gmail dot com>
Cc: gdb at sourceware dot org
Date: Thu, 23 Aug 2012 12:52:31 -0600
Subject: Re: GDB crashing because of Python
References: <CAPftXUJgcra=_exQY3po2AG7KjLSxm9dxkzu=Bsh2zO0eE1Ymw@mail.gmail.com> <87k3wpr9uy.fsf@fleche.redhat.com> <CAPftXULyovO08rghxQa2hO4RO8ssK6nt=O0g_abNUDo0OhPTCA@mail.gmail.com>

Kevin> I'm on Fedora 17, x86_64, Python seems to be at version 2.7.3, gdb is
Kevin> up to date against the trunk (7.5.50.20120823-cvs)

I installed F17 in a mock chroot and ran the latest gdb there.
This isn't an identical scenario due to possible kernel differences, but
I wouldn't expect those to matter.

>> Fatal Python error: GC object already tracked

Kevin> this one appears when I start the inferior execution, and start it again

I couldn't make it crash.
What happens if you run under valgrind?
When I do that, I see some output, but nothing that looks too serious
and/or new.

Tom

Follow-Ups:
- Re: GDB crashing because of Python
  - From: Kevin Pouget

References:
- GDB crashing because of Python
  - From: Kevin Pouget
- Re: GDB crashing because of Python
  - From: Tom Tromey
- Re: GDB crashing because of Python
  - From: Kevin Pouget

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]