public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: John Baldwin <jhb@FreeBSD.org>, gdb-patches@sourceware.org
Subject: Re: [PATCH 3/3] Per-inferior thread list, thread ranges/iterators, down with ALL_THREADS, etc.
Date: Thu, 04 Oct 2018 19:16:00 -0000	[thread overview]
Message-ID: <40fdd89a-d268-a788-ee56-ec21e39ff10b@redhat.com> (raw)
In-Reply-To: <c60ce6b4-8035-af87-e2a2-116b9afa90f9@FreeBSD.org>

On 10/03/2018 06:34 PM, John Baldwin wrote:
> On 10/2/18 6:21 AM, Pedro Alves wrote:
>> On 10/01/2018 05:33 PM, John Baldwin wrote:
>>> On 10/1/18 3:32 AM, Pedro Alves wrote:
>>>> As preparation for multi-target, this patch makes each inferior have
>>>> its own thread list.
>>>
>>> The BSD-related bits all look fine to me.  Do you have an existing branch
>>> for this on github that I can pull down to do some simple run-time testing?
>>
>> I've pushed it now to users/palves/per-inf-thread-list on sourceware.org.
> 
> I needed the following patch as a build fix, but it passed some simple
> testing of the native target:
> 
> diff --git a/gdb/bsd-kvm.c b/gdb/bsd-kvm.c
> index 078cd30c05..991b87852d 100644
> --- a/gdb/bsd-kvm.c
> +++ b/gdb/bsd-kvm.c
> @@ -25,7 +25,8 @@
>  #include "regcache.h"
>  #include "target.h"
>  #include "value.h"
> -#include "gdbcore.h"           /* for get_exec_file */
> +#include "gdbcore.h"
> +#include "inferior.h"          /* for get_exec_file */
>  #include "gdbthread.h"
>  
Thanks!  I've merged it into the patch, and force-pushed the
update to the branch.

Thanks,
Pedro Alves

  reply	other threads:[~2018-10-04 19:16 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-01 10:32 [PATCH 0/3] Per-inferior thread list, multi-target prep Pedro Alves
2018-10-01 10:32 ` [PATCH 1/3] Avoid find_thread_ptid with null_ptid Pedro Alves
2018-10-01 15:54   ` Tom Tromey
2018-10-02 17:08     ` Pedro Alves
2018-10-02 21:14       ` Tom Tromey
2018-10-01 10:33 ` [PATCH 3/3] Per-inferior thread list, thread ranges/iterators, down with ALL_THREADS, etc Pedro Alves
2018-10-01 16:33   ` John Baldwin
2018-10-02 13:21     ` Pedro Alves
2018-10-03 17:34       ` John Baldwin
2018-10-04 19:16         ` Pedro Alves [this message]
2018-10-01 17:12   ` Tom Tromey
2018-10-03 12:12     ` Pedro Alves
2018-10-01 10:33 ` [PATCH 2/3] Fix follow_exec latent problem Pedro Alves
2018-11-22 16:28 ` [PATCH 0/3] Per-inferior thread list, multi-target prep 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=40fdd89a-d268-a788-ee56-ec21e39ff10b@redhat.com \
    --to=palves@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=jhb@FreeBSD.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).