From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Pedro Alves <pedro@codesourcery.com>
Cc: gdb-patches@sourceware.org, Tom Tromey <tromey@redhat.com>
Subject: Re: FYI: fix 2 tests when glibc debuginfo is installed
Date: Sun, 16 Oct 2011 16:41:00 -0000 [thread overview]
Message-ID: <20111016115625.GA15749@host1.jankratochvil.net> (raw)
In-Reply-To: <20111014212510.GA20587@host1.jankratochvil.net>
On Fri, 14 Oct 2011 23:25:10 +0200, Jan Kratochvil wrote:
> Yes. But I do not think it is problem, one can SIGCONT it safely after
> PTRACE_DETACH. Just it may be (T)-stopped for a moment but why not.
>
> The opposite - the upstream 2.6.x kernel state - was IMO worse, it was resumed
> and one could not safely keep it stopped.
Without going into detail one can reach both states with new kernels, just the
default behavior has changed.
sleep 1h&p=$!;sleep 1;kill -STOP $p;sleep 1;grep ^State /proc/$p/status;./gdb -q -batch -p $p -ex q;sleep 1;grep ^State /proc/$p/status;kill -9 $p
GNU gdb (GDB) 7.3.50.20111016-cvs
kernel-2.6.35.14-96.fc14.x86_64:
State: T (stopped)
[... - GDB attach+detach]
State: S (sleeping)
kernel-3.1.0-0.rc6.git0.0.fc17.x86_64
State: T (stopped)
[... - GDB attach+detach]
State: T (stopped)
Regards,
Jan
prev parent reply other threads:[~2011-10-16 11:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-14 16:05 Tom Tromey
2011-10-14 19:37 ` Jan Kratochvil
2011-10-14 21:19 ` Pedro Alves
2011-10-14 21:25 ` Jan Kratochvil
2011-10-14 21:42 ` Pedro Alves
2011-10-15 14:52 ` Oleg Nesterov
2011-10-25 17:03 ` Pedro Alves
2011-10-25 17:38 ` Oleg Nesterov
2011-10-25 18:16 ` Pedro Alves
2011-10-25 18:38 ` Oleg Nesterov
2011-10-25 19:50 ` Pedro Alves
2011-10-16 16:41 ` Jan Kratochvil [this message]
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=20111016115625.GA15749@host1.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=pedro@codesourcery.com \
--cc=tromey@redhat.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