From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Pedro Alves <pedro@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [patch] regression: Quit should not ask with core (PR 12071)
Date: Thu, 30 Sep 2010 01:56:00 -0000 [thread overview]
Message-ID: <20100929221138.GA14109@host1.dyn.jankratochvil.net> (raw)
In-Reply-To: <201009291604.18270.pedro@codesourcery.com>
On Wed, 29 Sep 2010 17:04:17 +0200, Pedro Alves wrote:
> So, for example, if you have two inferiors in your gdb session, one of them
> is running as a process, while the other is still just a pseudo-inferior
> / file_stratum inferior yet, and you have the latter selected as current,
> your patch will make that have-live-inferiors check still return 0, while
> there _is_ one live inferior.
Confirming it had this problem.
No regressions on {x86_64,x86_64-m32,i686}-fedora14snapshot-linux-gnu.
Thanks,
Jan
gdb/
2010-09-29 Jan Kratochvil <jan.kratochvil@redhat.com>
* inferior.c (have_live_inferiors): New variables old_chain, inf and
tp. Iterate INFERIOR_LIST and call target_has_execution.
Gdb/testsuite/
2010-09-29 Jan Kratochvil <jan.kratochvil@redhat.com>
* gdb.base/corefile.exp (quit with a process, no question: load core)
(quit with a core file): New tests.
--- a/gdb/inferior.c
+++ b/gdb/inferior.c
@@ -461,16 +461,29 @@ have_inferiors (void)
int
have_live_inferiors (void)
{
- struct target_ops *t;
+ struct cleanup *old_chain;
+ struct inferior *inf;
- /* The check on stratum suffices, as GDB doesn't currently support
- multiple target interfaces. */
- if (have_inferiors ())
- for (t = current_target.beneath; t != NULL; t = t->beneath)
- if (t->to_stratum == process_stratum)
- return 1;
+ old_chain = make_cleanup_restore_current_thread ();
- return 0;
+ for (inf = inferior_list; inf; inf = inf->next)
+ if (inf->pid != 0)
+ {
+ struct thread_info *tp;
+
+ tp = any_thread_of_process (inf->pid);
+ if (tp)
+ {
+ switch_to_thread (tp->ptid);
+
+ if (target_has_execution)
+ break;
+ }
+ }
+
+ do_cleanups (old_chain);
+
+ return inf != NULL;
}
/* Prune away automatically added program spaces that aren't required
--- a/gdb/testsuite/gdb.base/corefile.exp
+++ b/gdb/testsuite/gdb.base/corefile.exp
@@ -201,8 +201,33 @@ gdb_test_multiple "info files" $test {
}
}
+set test "quit with a process"
+gdb_test_multiple "quit" $test {
+ -re "A debugging session is active.\r\n.*\r\nQuit anyway\\? \\(y or n\\) $" {
+ pass $test
+ gdb_test "n" {Not confirmed\.} "quit with processes: n"
+ }
+}
+
gdb_exit
+# Verify there is no question if only a core file is loaded.
+
+gdb_start
+gdb_test "core-file $corefile" "Core was generated by .*" "no question: load core"
+
+set test "quit with a core file"
+gdb_test_multiple "quit" $test {
+ -re "A debugging session is active.\r\n.*\r\nQuit anyway\\? \\(y or n\\) $" {
+ fail $test
+ gdb_test "n" {Not confirmed\.} "quit with processes: n"
+ }
+ eof {
+ pass $test
+ }
+}
+
+gdb_exit
# Test an attach command will clear any loaded core file.
next prev parent reply other threads:[~2010-09-29 22:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-29 16:44 Jan Kratochvil
2010-09-29 17:00 ` Pedro Alves
2010-09-30 1:56 ` Jan Kratochvil [this message]
2010-09-30 14:02 ` Pedro Alves
2010-09-30 14:43 ` Jan Kratochvil
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=20100929221138.GA14109@host1.dyn.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=pedro@codesourcery.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