Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Yao Qi <qiyaoltc@gmail.com>
To: Edjunior Machado <edjunior@gmail.com>
Cc: GDB Patches <gdb-patches@sourceware.org>
Subject: Re: ppc64* native-gdbserver testsuite hangs on gdb.threads/process-dies-while-handling-bp.exp
Date: Tue, 19 Dec 2017 17:51:00 -0000	[thread overview]
Message-ID: <86o9mu8v32.fsf@gmail.com> (raw)
In-Reply-To: <CAH=s-PO2vN4Gahajo5rNfSeSWRJsAEf_5r3yz-2Yw5jsMrXVaw@mail.gmail.com>	(Yao Qi's message of "Tue, 19 Dec 2017 16:27:04 +0000")

Yao Qi <qiyaoltc@gmail.com> writes:

> It is a known issue in GDB, described in PR 18749, rather than a
> regression, so git bisect can't tell you anything useful.  Pedro fixed
> one GDBserver crash caused by 18749, but PR 18749 is still
> there.
>
> I can reproduce the timeout on gcc110,
>
> KFAIL: gdb.threads/process-dies-while-handling-bp.exp: non_stop=on:
> cond_bp_target=0: inferior 1 exited (timeout) (PRMS: gdb/18749)
> Remote debugging from host 127.0.0.1^M
> gdbserver: reading register 10: No such process^M
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> Killing process(es): 15614^M
> monitor exit^M
> Ignoring packet error, continuing...
>
> I think some code path in GDBserver doesn't expect this error.

Does this patch work for you?  With this patch,
process-dies-while-handling-bp.exp never timeout on gcc110 with
native-gdbserver.

-- 
Yao (齐尧)
From ef027cdb366e3000dee2c713abab4f30123d9ed1 Mon Sep 17 00:00:00 2001
From: Yao Qi <yao.qi@linaro.org>
Date: Tue, 19 Dec 2017 17:44:11 +0000
Subject: [PATCH] Mark register unavailable when PTRACE_PEEKUSER fails

As described in PR 18749, GDB/GDBserver may get an error on accessing
memory or register because the thread may disappear.  However, some
path doesn't expect the error.  This patch fixes this problem by
marking the register unavailable when PTRACE_PEEKUSER fails instead
of throwing error.

gdb/gdbserver:

2017-12-19  Yao Qi  <yao.qi@linaro.org>

	PR gdb/18749
	* linux-low.c (fetch_register): Call supply_register instead of
	error.

diff --git a/gdb/gdbserver/linux-low.c b/gdb/gdbserver/linux-low.c
index f6a52d5..0a52a91 100644
--- a/gdb/gdbserver/linux-low.c
+++ b/gdb/gdbserver/linux-low.c
@@ -5555,7 +5555,11 @@ fetch_register (const struct usrregs_info *usrregs,
 		(PTRACE_TYPE_ARG3) (uintptr_t) regaddr, (PTRACE_TYPE_ARG4) 0);
       regaddr += sizeof (PTRACE_XFER_TYPE);
       if (errno != 0)
-	error ("reading register %d: %s", regno, strerror (errno));
+	{
+	  /* Mark register REGNO unavailable.  */
+	  supply_register (regcache, regno, NULL);
+	  return;
+	}
     }
 
   if (the_low_target.supply_ptrace_register)


  reply	other threads:[~2017-12-19 17:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-19  9:17 Edjunior Machado
2017-12-19 16:27 ` Yao Qi
2017-12-19 17:51   ` Yao Qi [this message]
2017-12-20 15:24     ` Edjunior Machado
2017-12-20 16:23       ` Yao Qi
2017-12-20 21:35         ` Yao Qi
2017-12-21 16:02           ` Edjunior Machado
2018-01-16  9:12     ` Yao Qi

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=86o9mu8v32.fsf@gmail.com \
    --to=qiyaoltc@gmail.com \
    --cc=edjunior@gmail.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