From: Tom Tromey <tromey@redhat.com>
To: Kevin Pouget <kevin.pouget@gmail.com>
Cc: gdb@sourceware.org
Subject: Re: GDB crashing because of Python
Date: Thu, 23 Aug 2012 13:56:00 -0000 [thread overview]
Message-ID: <87k3wpr9uy.fsf@fleche.redhat.com> (raw)
In-Reply-To: <CAPftXUJgcra=_exQY3po2AG7KjLSxm9dxkzu=Bsh2zO0eE1Ymw@mail.gmail.com> (Kevin Pouget's message of "Thu, 23 Aug 2012 15:21:13 +0200")
>>>>> "Kevin" == Kevin Pouget <kevin.pouget@gmail.com> writes:
Kevin> I notice today a lot for GDB crash because of Python, am I the
Kevin> only one? (I didn't refresh my git tree since a while, so it
Kevin> might not be directly related to the last Python patches)
Kevin> It's hard to tell exactly what cause it, but for instance I see
Kevin> repeatedly:
[...]
I haven't seen it.
I updated from CVS just now, rebuilt, and ran the gdb.python tests
without any problems.
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'm still on Fedora 16. I wouldn't expect 17 to have particular
problems like this though.
What were you doing when you got these crashes? Is it something simple
that I could try? What happens if you run the gdb.python tests?
Tom
next prev parent reply other threads:[~2012-08-23 13:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-23 13:21 Kevin Pouget
2012-08-23 13:56 ` Tom Tromey [this message]
2012-08-23 14:30 ` Kevin Pouget
2012-08-23 18:52 ` Tom Tromey
2012-08-27 16:05 ` Kevin Pouget
2012-08-27 16:36 ` Tom Tromey
2012-08-27 16:39 ` Tom Tromey
2012-08-28 19:45 ` Tom Tromey
2012-08-29 8:14 ` Kevin Pouget
2012-09-06 19:27 ` 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=87k3wpr9uy.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb@sourceware.org \
--cc=kevin.pouget@gmail.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).