Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <pedro@codesourcery.com>
To: gdb-patches@sourceware.org
Cc: Daniel Jacobowitz <drow@false.org>,
	 Roland McGrath <roland@redhat.com>,
	 Jan Kratochvil <jan.kratochvil@redhat.com>,
	 Doug Evans <dje@google.com>,
	 mark.kettenis@xs4all.nl
Subject: Re: [patch] Fix Linux attach to signalled/stopped processes
Date: Fri, 11 Apr 2008 22:21:00 -0000	[thread overview]
Message-ID: <200804112300.38076.pedro@codesourcery.com> (raw)
In-Reply-To: <20080411210221.GA13599@caradoc.them.org>

Some quick comments,

A Friday 11 April 2008 22:02:21, Daniel Jacobowitz wrote:

 > +  /* Pass on the last signal, if appropriate.  */
> +  if (lp->status == 0 && GET_LWP (lp->ptid) == GET_LWP (inferior_ptid)
> +      && stop_signal != TARGET_SIGNAL_0 && signal_pass_state (stop_signal))
> +    lp->status = W_STOPCODE (target_signal_to_host (stop_signal));

You're writing to lp->status of inferior_ptid, which isn't garantied
to be the main thread or the thread that got the last signal (user
may have used the "thread" command to switch threads, or we're stopped
at a breakpoint in some other thread not the main one, for example, or
the kernel decided to send the signal to some other thread because the
main one was already stopped?).

>   /* We don't actually detach from the LWP that has an id equal to the
>      overall process id just yet.  */
>   if (GET_LWP (lp->ptid) != GET_PID (lp->ptid))
>@@ -1263,14 +1343,29 @@ static void
> linux_nat_detach (char *args, int from_tty)
> {
>   int pid;
>+  int status;
>+  enum target_signal sig;
>+
>   if (target_can_async_p ())
>     linux_nat_async (NULL, 0);
> 
>-  iterate_over_lwps (detach_callback, NULL);
>+  iterate_over_lwps (detach_callback, &status);
>

Passing &status seems bogus, since you're passing the status
in lp->status ?
 
>   /* Only the initial process should be left right now.  */
>   gdb_assert (num_lwps == 1);
> 
>+  /* Pass on any pending signal for the last LWP.  */
>+  status = lwp_list->status;
>+  if (WIFSTOPPED (status) && (args == NULL || *args == '\0'))
>+    {
>+      args = alloca (8);
>+      sprintf (args, "%d", (int) WSTOPSIG (status));
>+      fprintf_unfiltered (gdb_stdlog,
>+                         "LND: Sending signal %s to %s\n",
>+                         args,
>+                         target_pid_to_str (lwp_list->ptid));
>+    }
>+
>

I don't see where you're actually sending the signal.  Even if you
did, it isn't guarantied you are passing this signal.  It will miss it
if inferior_ptid isn't the main thread.  See comments above.

Also, why the alloca dance instead of using
"Sending signal %d to %s\n" directly, if you're not doing anything
else with args?  AKA, what's the plan for args?

What's supposed to happen if stop_signal was a SIGTRAP ?

-- 
Pedro Alves


  reply	other threads:[~2008-04-11 22:01 UTC|newest]

Thread overview: 52+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-31 22:07 Doug Evans
2008-04-02  0:01 ` Jan Kratochvil
2008-04-02  0:07   ` Roland McGrath
2008-04-10 15:30     ` Daniel Jacobowitz
2008-04-10 15:37       ` Jan Kratochvil
2008-04-10 15:49         ` Daniel Jacobowitz
2008-04-10 16:00           ` Jan Kratochvil
2008-04-10 19:59             ` Daniel Jacobowitz
2008-04-10 15:39   ` Daniel Jacobowitz
2008-04-10 16:00     ` Jan Kratochvil
2008-04-10 19:48       ` Daniel Jacobowitz
2008-04-11  8:46       ` Roland McGrath
2008-04-11 17:46         ` Jan Kratochvil
2008-04-11 19:01           ` Daniel Jacobowitz
2008-04-12  7:58           ` Roland McGrath
2008-04-14 15:09             ` Daniel Jacobowitz
2008-04-14 15:31               ` Daniel Jacobowitz
2008-04-15 22:14                 ` Jan Kratochvil
2008-05-01 18:50                   ` Daniel Jacobowitz
2008-07-05  8:48                     ` Jan Kratochvil
2008-07-05 13:48                       ` Daniel Jacobowitz
2008-09-24 12:46                 ` Andreas Schwab
2008-09-26  3:52                   ` Jan Kratochvil
2008-09-26 13:00                     ` Daniel Jacobowitz
2008-09-28 11:43                       ` Jan Kratochvil
2008-09-28 14:58                         ` Daniel Jacobowitz
2008-04-15  8:14               ` Roland McGrath
2008-04-15 13:02                 ` Daniel Jacobowitz
2008-04-16  7:01                   ` Roland McGrath
2008-04-11 22:20         ` Daniel Jacobowitz
2008-04-11 22:21           ` Pedro Alves [this message]
2008-04-11 22:25             ` Daniel Jacobowitz
2008-04-12  0:02               ` Pedro Alves
2008-04-12  0:19                 ` Pedro Alves
2008-04-13  9:35                   ` Pedro Alves
2008-04-13 13:40                     ` Pedro Alves
2008-04-12 16:38           ` Roland McGrath
2008-04-12 16:43           ` Eli Zaretskii
  -- strict thread matches above, loose matches on Subject: below --
2007-06-06 14:34 Jan Kratochvil
2007-06-11 13:44 ` Jan Kratochvil
2007-06-15 18:02 ` Mark Kettenis
2007-06-26 22:40   ` Jan Kratochvil
2007-06-27  0:13     ` Mark Kettenis
2007-06-27 11:59       ` Jan Kratochvil
2007-06-27 18:30         ` Mark Kettenis
2007-06-30 11:45         ` Jan Kratochvil
2007-06-30 11:57           ` Eli Zaretskii
2007-06-30 17:15             ` Jan Kratochvil
2007-06-30 18:52               ` Eli Zaretskii
     [not found]               ` <200706301852.l5UIq8ek010536@brahms.sibelius.xs4all.nl>
2007-07-01  3:17                 ` Eli Zaretskii
2007-07-01  9:34                   ` Mark Kettenis
2007-07-01 10:03                     ` 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=200804112300.38076.pedro@codesourcery.com \
    --to=pedro@codesourcery.com \
    --cc=dje@google.com \
    --cc=drow@false.org \
    --cc=gdb-patches@sourceware.org \
    --cc=jan.kratochvil@redhat.com \
    --cc=mark.kettenis@xs4all.nl \
    --cc=roland@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