Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Phil Muldoon <pmuldoon@redhat.com>
To: "Ömer Sinan Ağacan" <omeragacan@gmail.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:20:00 -0000	[thread overview]
Message-ID: <54412597.8080600@redhat.com> (raw)
In-Reply-To: <CAMQQO3mVQX8S7_juz2XgNQEjJWnYMWyAXMYVS93Kr2epo8a6Gw@mail.gmail.com>

On 17/10/14 11:52, Ömer Sinan Ağacan wrote:
> IMO, something like dont_block would be more useful for me. What I would expect
> from that argument is that when it's True then `gdb.execute` would return
> immediately after GDB starts running the command.
>
>> A workaround would be to post any gdb.execute statements into the GDB event
>> loop.  See gdb.post_event.  That will return immediately and the gdb.execute
>> function will be scheduled to be called in the event loop.  Note there is no
>> guarantee when this is.  But as long as GDB is not busy processing other
>> events it usually means right away.

> Do you think adding something like `dont_block` would be hard? Maybe I can hack
> on that this weekend.

Hi,

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

Cheers

Phil


  reply	other threads:[~2014-10-17 14:20 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 [this message]
2014-10-17 14:27                   ` Ömer Sinan Ağacan
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=54412597.8080600@redhat.com \
    --to=pmuldoon@redhat.com \
    --cc=Paul_Koning@dell.com \
    --cc=gdb@sourceware.org \
    --cc=omeragacan@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