From: Andrew Cagney <ac131313@redhat.com>
To: Elena Zannoni <ezannoni@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFC] PTRACE_ATTACH problem on new Linux kernels
Date: Wed, 19 Feb 2003 17:16:00 -0000 [thread overview]
Message-ID: <3E53BCFA.70405@redhat.com> (raw)
In-Reply-To: <15954.39904.805543.819269@localhost.redhat.com>
> Kind of. I am testing the following:
>
> 2003-02-18 Elena Zannoni <ezannoni@redhat.com>
>
> * infrun.c (stop_soon_quietly): Make it an enum, to better
> override the default behavior of handle_inferior_event.
> (clear_proceed_status): Update uses of stop_soon_quietly to
> reflect that it is now an enum.
> (start_remote): Ditto.
> (handle_inferior_event): Change logic a bit if stop_soon_quietly
> is set to handle the new kernel behavior for attach/sigstop.
> Update uses of stop_soon_quietly.
> * inferior.h (enum stop_kind): New enum.
> * infcmd.c (attach_command): Use STOP_QUIETLY_NO_SIGSTOP.
> Reset normal handle_inferior_event behavior, afterwards.
> * fork-child.c (startup_inferior): Update.
> * alpha-tdep.c (heuristic_proc_start): Update.
> * solib-svr4.c (svr4_solib_create_inferior_hook): Update.
> * solib-sunos.c (sunos_solib_create_inferior_hook): Update.
> * solib-osf.c (osf_solib_create_inferior_hook): Update.
> * solib-irix.c (irix_solib_create_inferior_hook): Update.
> * remote-vx.c (vx_create_inferior): Update.
> * mips-tdep.c (heuristic_proc_start): Update.
Yes, anything like this. Only one state variable to contend with.
Andrew
next prev parent reply other threads:[~2003-02-19 17:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-18 0:53 Elena Zannoni
2003-02-18 2:39 ` Andrew Cagney
2003-02-18 3:14 ` Daniel Jacobowitz
2003-02-18 3:32 ` Elena Zannoni
2003-02-19 17:19 ` Andrew Cagney
2003-02-19 17:28 ` Daniel Jacobowitz
2003-02-18 3:28 ` Elena Zannoni
2003-02-18 20:06 ` Andrew Cagney
2003-02-18 20:43 ` Elena Zannoni
2003-02-19 17:16 ` Andrew Cagney [this message]
2003-02-19 17:40 ` Kevin Buettner
2003-04-08 18:53 ` Elena Zannoni
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=3E53BCFA.70405@redhat.com \
--to=ac131313@redhat.com \
--cc=ezannoni@redhat.com \
--cc=gdb-patches@sources.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