Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Atsushi Nemoto <anemo@mba.ocn.ne.jp>
To: drow@false.org
Cc: gdb-patches@sources.redhat.com
Subject: Re: remote debugging a multi-threaded program with signal
Date: Fri, 05 Mar 2004 16:36:00 -0000	[thread overview]
Message-ID: <20040306.014343.74756819.anemo@mba.ocn.ne.jp> (raw)
Message-ID: <20040305163600.fxQ_UMxGt0VoI3kQnQASs3ndWAswKNeTRFOxLxIjX48@z> (raw)
In-Reply-To: <20040305.112722.74754522.nemoto@toshiba-tops.co.jp>

>>>>> On Fri, 05 Mar 2004 11:27:22 +0900 (JST), Atsushi Nemoto <anemo@mba.ocn.ne.jp> said:

anemo> How about when verbose-resume was disabled or unavailable?  If
anemo> verbose-resume is necessary to continue with signal, gdb can
anemo> warn it for users?  Or gdbserver can resume all threads on this
anemo> case?

For gdb without verbose-resume, how about this patch?  With this
patch, gdbserver uses general_thread instead of all_threads.head if
'CNN' packet was sent without preceding 'HcNN'.

--- gdb-6.0.90.org/gdb/gdbserver/target.c	Wed Jun 12 02:32:40 2002
+++ gdb-6.0.90/gdb/gdbserver/target.c	Sat Mar  6 01:29:44 2004
@@ -49,6 +49,10 @@ set_desired_inferior (int use_general)
       if (found == NULL)
 	found = (struct thread_info *) find_inferior_id (&all_threads,
 							 cont_thread);
+      /* failsafe: use thread in last resume_reply */
+      if (found == NULL)
+	found = (struct thread_info *) find_inferior_id (&all_threads,
+							 general_thread);
     }
 
   if (found == NULL)

---
Atsushi Nemoto


  parent reply	other threads:[~2004-03-05 16:36 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-03 15:59 Atsushi Nemoto
2004-03-19  0:09 ` Atsushi Nemoto
2004-03-04 14:58   ` Atsushi Nemoto
2004-03-04 22:28   ` Daniel Jacobowitz
2004-03-19  0:09     ` Daniel Jacobowitz
2004-03-19  0:09     ` Atsushi Nemoto
2004-03-05  2:25       ` Atsushi Nemoto
2004-03-19  0:09       ` Atsushi Nemoto [this message]
2004-03-05 16:36         ` Atsushi Nemoto
2004-03-05 16:38         ` Daniel Jacobowitz
2004-03-06 12:42           ` Atsushi Nemoto
2004-03-19  0:09             ` Atsushi Nemoto
2004-03-19  0:09             ` Daniel Jacobowitz
2004-03-06 17:11               ` Daniel Jacobowitz
2004-03-07 14:14               ` Atsushi Nemoto
2004-03-19  0:09                 ` Atsushi Nemoto
2004-03-19  0:09           ` Daniel Jacobowitz
2004-03-19  0:09     ` Atsushi Nemoto
2004-03-05  4:15       ` Atsushi Nemoto
2004-03-19  0:09 ` Atsushi Nemoto

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=20040306.014343.74756819.anemo@mba.ocn.ne.jp \
    --to=anemo@mba.ocn.ne.jp \
    --cc=drow@false.org \
    --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