public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "dje at google dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/17223] cannot do background execution in scripts
Date: Fri, 01 Aug 2014 19:58:00 -0000	[thread overview]
Message-ID: <bug-17223-4717-2vzRxDVoQ7@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-17223-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=17223

--- Comment #3 from dje at google dot com ---
(In reply to dje from comment #1)
> A potential hacky workaround is to feed the script to stdin.
> One may need to do "set interactive-mode on".
> But see pr 17224, currently trying this segvs.

As an experiment, I find I can get gdb to process inferior events if I add
enough nops to the script.  E.g., do "info threads", do some mindless things
like "pwd", do another "info threads", etc. and slowly the threads start to
appear.

In this case stdin is "hogging" the event queue.
IWBN, at least in this case, if inferior events hogged the event queue.
Are there some cases where we want the former and some where we want the
latter?
Or can we, for example, keep processing inferior events until there are no
more?

It may be that some command ("wait" or whatever) that one can put in a script
to explicitly process all current inferior events has sufficient utility to
warrant adding.

-- 
You are receiving this mail because:
You are on the CC list for the bug.


  parent reply	other threads:[~2014-08-01 19:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-01 18:12 [Bug gdb/17223] New: " dje at google dot com
2014-08-01 19:19 ` [Bug gdb/17223] " dje at google dot com
2014-08-01 19:51 ` dje at google dot com
2014-08-01 19:58 ` dje at google dot com [this message]
2015-01-14  9:18 ` palves at redhat dot com

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=bug-17223-4717-2vzRxDVoQ7@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@sourceware.org \
    /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).