aboutsummaryrefslogtreecommitdiff
path: root/gdb/testsuite/gdb.fortran
diff options
context:
space:
mode:
authorPedro Alves <palves@redhat.com>2014-07-14 19:55:32 +0100
committerPedro Alves <palves@redhat.com>2014-07-14 20:33:16 +0100
commit93d6eb10ede1d8b72b274345c63f66439eaf7fd0 (patch)
treed6a6f986d064b31bd7f1572ae207ca8bf62f4aab /gdb/testsuite/gdb.fortran
parent0017922d0292d8c374584f6100874580659c9973 (diff)
downloadgdb-93d6eb10ede1d8b72b274345c63f66439eaf7fd0.zip
gdb-93d6eb10ede1d8b72b274345c63f66439eaf7fd0.tar.gz
gdb-93d6eb10ede1d8b72b274345c63f66439eaf7fd0.tar.bz2
Remove the target from the event loop while in secondary prompts
If a pagination prompt triggers while the target is running, and the target exits before the user responded to the pagination query, this happens: Starting program: foo ---Type <return> to continue, or q <return> to quit---No unwaited-for children left. Couldn't get registers: No such process. Couldn't get registers: No such process. Couldn't get registers: No such process. (gdb) Couldn't get registers: No such process. (gdb) To reiterate, the user hasn't replied to the pagination prompt above. A pagination query nests an event loop (in gdb_readline_wrapper). In async mode, in addition to stdin and signal handlers, we'll have the target also installed in the event loop still. So if the target reports an event, that wakes up the nested event loop, which calls into fetch_inferior_event etc. to handle the event which generates further output, all while we should be waiting for pagination confirmation... (TBC, any target event that generates output ends up spuriously waking up the pagination, though exits seem to be the worse kind.) I've played with a couple different approaches to fixing this, while at the same time trying to avoid being invasive. Both revolve around not listening to target events while in a pagination prompt (doing anything else I think would be a much bigger change). The approach taken just removes the target from the event loop while within gdb_readline_wrapper. The other approach used gdb_select directly, with only input_fd installed, but that had the issue that it didn't handle the async signal handlers, and turned out to be a bit more code than the first version. gdb/ 2014-07-14 Pedro Alves <palves@redhat.com> PR gdb/17072 * top.c: Include "inf-loop.h". (struct gdb_readline_wrapper_cleanup) <target_is_async_orig>: New field. (gdb_readline_wrapper_cleanup): Make the target async again, if it was async before. (gdb_readline_wrapper): Store whether the target is async, and make it sync. gdb/testsuite/ 2014-07-14 Pedro Alves <palves@redhat.com> PR gdb/17072 * gdb.base/paginate-inferior-exit.c: New file. * gdb.base/paginate-inferior-exit.exp: New file.
Diffstat (limited to 'gdb/testsuite/gdb.fortran')
0 files changed, 0 insertions, 0 deletions