Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: John Baldwin <jhb@freebsd.org>
To: gdb-patches@sourceware.org
Cc: Pedro Alves <palves@redhat.com>,
	Paul_Koning@dell.com, binutils@sourceware.org
Subject: Re: [PATCH 0/6] Support kernel-backed user threads on FreeBSD
Date: Tue, 12 Jan 2016 21:08:00 -0000	[thread overview]
Message-ID: <2188756.HMZ3O5MULv@ralph.baldwin.cx> (raw)
In-Reply-To: <569552FD.6080304@redhat.com>

On Tuesday, January 12, 2016 07:24:45 PM Pedro Alves wrote:
> On 01/12/2016 07:06 PM, Paul_Koning@Dell.com wrote:
> > 
> >> On Jan 12, 2016, at 1:55 PM, John Baldwin <jhb@freebsd.org> wrote:
> >>
> >> On Monday, January 11, 2016 10:53:50 AM John Baldwin wrote:
> 
> >> One other note I forgot to mention is that currently I leave the ptid for
> >> single-threaded processes as (pid, 0, 0) (i.e. I only use LWPs in PTIDs
> >> when there is more than one thread).  What is the best practice?  Should
> >> I always use LWPs in ptids instead?
> > 
> > I would say always use the LWP.
> > 
> > For one thing, the process might start out single-threaded, then at some point midway through the debug session start more threads.  If you always use the LWP, the main thread doesn't change identity.  But if you fake the PTID to (pid,0,0) then that ID no longer applies once the new thread starts.  You'd end up with the confusion of apparently seeing a thread disappear and a new one appear in its place, when in reality that's just the main thread continuing in existence.
> 
> We have thread_change_ptid to handle that scenario, but it's indeed best
> to avoid it if possible.

Yes, I use that now.  However, I will update it to switch to LWPs always
and re-post (with --threaded this time).

-- 
John Baldwin


      reply	other threads:[~2016-01-12 21:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-11 18:53 John Baldwin
2016-01-12 18:55 ` John Baldwin
2016-01-12 19:06   ` Mark Kettenis
2016-01-12 19:07   ` Paul_Koning
2016-01-12 19:24     ` Pedro Alves
2016-01-12 21:08       ` John Baldwin [this message]

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=2188756.HMZ3O5MULv@ralph.baldwin.cx \
    --to=jhb@freebsd.org \
    --cc=Paul_Koning@dell.com \
    --cc=binutils@sourceware.org \
    --cc=gdb-patches@sourceware.org \
    --cc=palves@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