Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jon Turney <jon.turney@dronecode.org.uk>
To: gdb-patches@sourceware.org
Subject: Re: [PATCH] Consolidate target_mourn_inferior between GDB and gdbserver
Date: Fri, 23 Sep 2016 13:59:00 -0000	[thread overview]
Message-ID: <03f09c13-9fec-ee9a-adf9-95e9f0e81b91@dronecode.org.uk> (raw)
In-Reply-To: <87h99cjzd0.fsf@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 1082 bytes --]

On 19/09/2016 05:19, Sergio Durigan Junior wrote:
> On Thursday, September 15 2016, Pedro Alves wrote:
>> On 09/12/2016 05:51 AM, Sergio Durigan Junior wrote:
>> Thanks, patch is OK.
>>
>>> I'd appreciate a special look at gdb/windows-nat.c's modification
>>> because I wasn't really sure what to do there.  It seemed to me that
>>> maybe I should build a ptid out of the process information there, but
>>> then I am almost sure the assertion on GDB's side would trigger.
>>
>> Just leave it passing inferior_ptid like all other places, which is
>> a no-op.  We're certain the assertion does not fail this way.
>
> Thanks, pushed.
>
>   bc1e6c81d5b77d78282c47f6fd7f697e564a6eb6

This seems to miss one use of target_mourn_inferior() in windows-nat.c.

> ../../gdb/windows-nat.c: In function ‘void windows_kill_inferior(target_ops*)’:
> ../../gdb/windows-nat.c:2467:26: error: too few arguments to function ‘void target_mourn_inferior(ptid_t)’
>    target_mourn_inferior (); /* Or just windows_mourn_inferior?  */
>                           ^

Patch attached.



[-- Attachment #2: 0001-Fix-a-use-of-target_mourn_inferior-in-windows-nat.c.patch --]
[-- Type: text/plain, Size: 1461 bytes --]

From 75869cf539056bcff2351f698ccf79286d137cfb Mon Sep 17 00:00:00 2001
From: Jon Turney <jon.turney@dronecode.org.uk>
Date: Fri, 23 Sep 2016 14:07:55 +0100
Subject: [PATCH] Fix a use of target_mourn_inferior in windows-nat.c

One use of target_mourn_interior seems to have been missed in bc1e6c81

gdb/ChangeLog:

2016-09-23  Jon Turney  <jon.turney@dronecode.org.uk>

	* windows-nat.c (windows_delete_thread): Adjusting call to
	target_mourn_inferior to include ptid_t argument.

Signed-off-by: Jon Turney <jon.turney@dronecode.org.uk>
---
 gdb/ChangeLog     | 5 +++++
 gdb/windows-nat.c | 2 +-
 2 files changed, 6 insertions(+), 1 deletion(-)

diff --git a/gdb/ChangeLog b/gdb/ChangeLog
index ea14f04..c7a194f 100644
--- a/gdb/ChangeLog
+++ b/gdb/ChangeLog
@@ -1,3 +1,8 @@
+2016-09-23  Jon Turney  <jon.turney@dronecode.org.uk>
+
+	* windows-nat.c (windows_delete_thread): Adjusting call to
+	target_mourn_inferior to include ptid_t argument.
+
 2016-09-22  Edjunior Barbosa Machado  <emachado@linux.vnet.ibm.com>
 
 	* rs6000-tdep.c (ppc_process_record_op31): Fix
diff --git a/gdb/windows-nat.c b/gdb/windows-nat.c
index 31a9ecb..c6a809b 100644
--- a/gdb/windows-nat.c
+++ b/gdb/windows-nat.c
@@ -2464,7 +2464,7 @@ windows_kill_inferior (struct target_ops *ops)
 	break;
     }
 
-  target_mourn_inferior ();	/* Or just windows_mourn_inferior?  */
+  target_mourn_inferior (inferior_ptid);	/* Or just windows_mourn_inferior?  */
 }
 
 static void
-- 
2.8.3


  parent reply	other threads:[~2016-09-23 13:17 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-12  4:52 Sergio Durigan Junior
2016-09-15 15:51 ` Pedro Alves
2016-09-19  4:19   ` Sergio Durigan Junior
2016-09-19 14:39     ` Pedro Alves
2016-09-19 17:07       ` Sergio Durigan Junior
2016-09-20 11:13       ` [PATCH] Use 'event_ptid' instead of 'resume_ptid' on startup_inferior (fix for regression on my last commit) Sergio Durigan Junior
2016-09-20 11:18         ` Pedro Alves
2016-09-20 12:32           ` Sergio Durigan Junior
2016-09-23 13:59     ` Jon Turney [this message]
2016-09-23 15:45       ` [PATCH] Consolidate target_mourn_inferior between GDB and gdbserver Pedro Alves

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=03f09c13-9fec-ee9a-adf9-95e9f0e81b91@dronecode.org.uk \
    --to=jon.turney@dronecode.org.uk \
    --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