From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Pedro Alves <pedro@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Regression for T (Stopped) processes [Re: [PATCH] PR threads/10729: x86 hw watchpoints and non-stop mode]
Date: Thu, 15 Dec 2011 08:48:00 -0000 [thread overview]
Message-ID: <20111215062013.GA13506@host2.jankratochvil.net> (raw)
In-Reply-To: <201112141734.43226.pedro@codesourcery.com>
On Wed, 14 Dec 2011 18:34:43 +0100, Pedro Alves wrote:
> --- a/gdb/gdbserver/linux-low.c
> +++ b/gdb/gdbserver/linux-low.c
> @@ -918,6 +918,8 @@ linux_detach_one_lwp (struct inferior_list_entry *entry, void *args)
> get_lwp_thread (lwp));
>
> /* Finally, let it resume. */
> + if (the_low_target.prepare_to_resume != NULL)
> + the_low_target.prepare_to_resume (lwp);
> ptrace (PTRACE_DETACH, lwpid_of (lwp), 0, 0);
>
> delete_lwp (lwp);
If you have T (Stopped) process on Linux kernel 3.1+, you do attach,
bt/gcore/etc., detach, the state of the process must not change.
But the process will now run for a bit.
This is a regression. Some users really insist the T (Stopped) inferior state
absolutely does not change.
Thanks,
Jan
next prev parent reply other threads:[~2011-12-15 6:20 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-05 16:46 [PATCH] PR threads/10729: x86 hw watchpoints and non-stop mode Pedro Alves
2011-12-05 17:06 ` Eli Zaretskii
2011-12-09 16:30 ` New tests to watch regions larger than a machine word (Re: [PATCH] PR threads/10729: x86 hw watchpoints and non-stop mode) Pedro Alves
2011-12-09 19:11 ` Eli Zaretskii
2011-12-13 16:12 ` Pedro Alves
2011-12-05 21:24 ` [PATCH] PR threads/10729: x86 hw watchpoints and non-stop mode Jan Kratochvil
2011-12-09 16:45 ` Pedro Alves
2011-12-09 16:47 ` Tristan Gingold
2011-12-09 19:23 ` Eli Zaretskii
2011-12-13 16:26 ` Pedro Alves
2011-12-11 23:39 ` Jan Kratochvil
2011-12-12 11:53 ` Pedro Alves
2011-12-12 14:49 ` Jan Kratochvil
2011-12-12 0:14 ` Jan Kratochvil
2011-12-12 17:23 ` Pedro Alves
2011-12-12 18:38 ` Jan Kratochvil
2011-12-12 20:14 ` Jan Kratochvil
2011-12-12 20:30 ` Pedro Alves
2011-12-13 17:24 ` Jan Kratochvil
2011-12-13 18:49 ` Pedro Alves
2011-12-13 19:25 ` Jan Kratochvil
2011-12-16 16:16 ` Pedro Alves
2012-01-20 19:51 ` testsuite: native/non-extended/extended modes [Re: [PATCH] PR threads/10729: x86 hw watchpoints and non-stop mode] Jan Kratochvil
2012-01-20 19:53 ` Pedro Alves
2012-01-20 19:57 ` Jan Kratochvil
2011-12-12 20:34 ` [PATCH] PR threads/10729: x86 hw watchpoints and non-stop mode Pedro Alves
2011-12-12 21:39 ` Jan Kratochvil
2011-12-13 16:21 ` Fix PR remote/13492 (Re: [PATCH] PR threads/10729: x86 hw watchpoints and non-stop mode) Pedro Alves
2011-12-13 17:23 ` Fix PR remote/13492 Jan Kratochvil
2011-12-13 16:33 ` [PATCH] PR threads/10729: x86 hw watchpoints and non-stop mode Pedro Alves
2011-12-13 18:57 ` Jan Kratochvil
2011-12-14 17:35 ` Pedro Alves
2011-12-14 17:42 ` Pedro Alves
2011-12-15 8:48 ` Jan Kratochvil [this message]
2011-12-15 12:44 ` Regression for T (Stopped) processes [Re: [PATCH] PR threads/10729: x86 hw watchpoints and non-stop mode] Pedro Alves
2011-12-15 15:33 ` Jan Kratochvil
2011-12-13 22:27 ` [PATCH] PR threads/10729: x86 hw watchpoints and non-stop mode 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=20111215062013.GA13506@host2.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