From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: gdb-patches@sourceware.org
Subject: Re: [patch] Fix attaching to Linux stopped processes
Date: Mon, 18 Sep 2006 20:49:00 -0000 [thread overview]
Message-ID: <20060918204912.GA1869@host0.dyn.jankratochvil.net> (raw)
In-Reply-To: <20060918131616.GA22307@nevyn.them.org>
On Mon, 18 Sep 2006 15:16:17 +0200, Daniel Jacobowitz wrote:
...
> > Also the patch looks right to me - after `PT_ATTACH' it is appropriate that
> > `WSTOPSIG (status)' will report the original signal that stopped process,
> > (WSTOPSIG (status) == SIGSTOP) <=> (process was in running/sleeping mode).
>
> The part I was dubious about was the zero if already stopped by
> sigstop.
[ see below ]
> In any case, I agree. The patch to linux-nat.c is OK to apply.
>
> I'm not sure about the testcase though :-( I don't think it'll work
> without the RH patched kernel, will it?
The testcase does not work for kernel.org kernels.
And in fast on kernel.org Linux kernels the patch also does not work well as
you need to manually "kill -CONT" the process during the attach, moreover gdb
will get 'SIGCONT' id afterwards (and leave the process running after detach).
(I did not test but) I expect the Red Hat kernels behavior change is due to the
new utrace patch from Intel present in Red Hat kernels. It is going to be
imported to kernel.org one day changing the current (IMO broken - I may be
wrong) kernels behavior.
Still I consider the patch to be better than the current behavior but still it
is not fully functional, sorry for its submission; going to check the patches
on kernel.org kernels next time. Patch update from me possible later.
Regards,
Jan
next prev parent reply other threads:[~2006-09-18 20:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-17 22:12 Jan Kratochvil
2006-09-17 22:26 ` Daniel Jacobowitz
2006-09-18 9:53 ` Jan Kratochvil
2006-09-18 13:16 ` Daniel Jacobowitz
2006-09-18 20:49 ` Jan Kratochvil [this message]
2006-09-18 20:54 ` Daniel Jacobowitz
2006-09-23 17:37 ` Mark Kettenis
2006-09-25 10:52 ` 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=20060918204912.GA1869@host0.dyn.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=gdb-patches@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