From: "Ömer Sinan Ağacan" <omeragacan@gmail.com>
To: Phil Muldoon <pmuldoon@redhat.com>
Cc: paul_koning <Paul_Koning@dell.com>, gdb <gdb@sourceware.org>
Subject: Re: recursion limit exceeded in Python API, but there's only one function in traceback
Date: Fri, 17 Oct 2014 14:27:00 -0000 [thread overview]
Message-ID: <CAMQQO3nN_=dshUzwV=cWi2DRg-DtKGuQ4tnT2Lc8KSxfaiSSqg@mail.gmail.com> (raw)
In-Reply-To: <54412597.8080600@redhat.com>
> The patch has already been written (I had to fix it for a RH bugzilla
> entry). I just have not gotten around to posting it upstream yet. I
> will do that very soon. But if you are interested, the patch is here:
>
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1116957
Can anyone explain me how does GIL related with my problem? A blocking call
will still be blocking no matter what happens to GIL, I don't understand how
`gdb.execute("continue")` won't fill the stack with free GIL.
next prev parent reply other threads:[~2014-10-17 14:27 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-16 10:46 Ömer Sinan Ağacan
2014-10-16 12:45 ` Phil Muldoon
2014-10-16 14:28 ` Paul_Koning
[not found] ` <CAMQQO3=GxjGzF-9RXQsJ_9=Du3rS-UoYFA_0-friPp1nMa8yAA@mail.gmail.com>
2014-10-16 15:04 ` Paul_Koning
2014-10-16 15:15 ` Ömer Sinan Ağacan
2014-10-16 15:18 ` Ömer Sinan Ağacan
2014-10-17 9:31 ` Ömer Sinan Ağacan
2014-10-17 10:11 ` Phil Muldoon
2014-10-17 10:53 ` Ömer Sinan Ağacan
2014-10-17 14:20 ` Phil Muldoon
2014-10-17 14:27 ` Ömer Sinan Ağacan [this message]
2014-10-17 15:02 ` Phil Muldoon
2014-10-17 15:04 ` Paul_Koning
2014-10-17 17:31 ` Phil Muldoon
2014-10-17 16:41 ` Doug Evans
2014-10-17 17:35 ` Phil Muldoon
2014-10-17 16:45 ` Doug Evans
[not found] ` <543FE072.6040507@redhat.com>
2014-10-16 15:16 ` Ömer Sinan Ağacan
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='CAMQQO3nN_=dshUzwV=cWi2DRg-DtKGuQ4tnT2Lc8KSxfaiSSqg@mail.gmail.com' \
--to=omeragacan@gmail.com \
--cc=Paul_Koning@dell.com \
--cc=gdb@sourceware.org \
--cc=pmuldoon@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