Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Pedro Alves <pedro@codesourcery.com>
Cc: Ulrich Weigand <uweigand@de.ibm.com>, gdb-patches@sourceware.org
Subject: Re: [rfc] Preferred thread event reporting: Linux native target
Date: Mon, 18 Aug 2008 16:23:00 -0000	[thread overview]
Message-ID: <20080818162300.GA20375@caradoc.them.org> (raw)
In-Reply-To: <200808152354.32763.pedro@codesourcery.com>

On Fri, Aug 15, 2008 at 11:54:31PM +0100, Pedro Alves wrote:
> > > For my series to go in, every target much register at least the main
> > > thread in GDB's thread tables, and as it happens, I think AIX
> > > is the only target I don't have covered, or that I know of
> > > no one covering.
> >
> > I can test AIX if necessary.  Do you have a patch?
> 
> I stratched my head quite a bit staring at aix-thread.c/sync_threadlists
> and its use of ptid_cmp.  I still can't tell if/what I should do there.
> Also, I can't tell if rs6000_wait can ever return a ptid
> different from pid_to_ptid(main_process_pid), (or -1).
> 
> Basically, I need to:
> 
>  1) make sure the core never gets a thread related event
>     that corresponds to a thread the core doesn't know
>     about yet.
> 
>  2) #1 implies that every target should register the main
>    thread, even when debugging a single-threaded app.
>    rs6000-nat.c, being a ptrace based target, already has that
>    covered by these:
>     http://sourceware.org/ml/gdb-patches/2008-08/msg00170.html
>     http://sourceware.org/ml/gdb-patches/2008-08/msg00171.html
> 
>  3) #2 implies that a thread_stratum layer should decorate the
>     main thread's ptid with thread id info, instead of adding it
>     again. That's thread_change_ptid from:    
>     http://sourceware.org/ml/gdb-patches/2008-08/msg00170.html

Ulrich, I don't suppose I could ask you to do this?  Pedro's already
done a heroic job fixing up other targets... Pedro, I know you started
looking at AIX; maybe you have a patch that at least points out the
places that need to change?

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2008-08-18 16:23 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-14 20:40 Ulrich Weigand
2008-08-14 21:20 ` Pedro Alves
2008-08-14 21:51   ` Ulrich Weigand
2008-08-15 18:22     ` Michael Snyder
2008-08-18 16:01       ` Ulrich Weigand
2008-08-15 23:28     ` Pedro Alves
2008-08-18 16:23       ` Daniel Jacobowitz [this message]
2008-08-18 17:01         ` Ulrich Weigand
2008-08-18 17:04           ` Daniel Jacobowitz
2008-08-18 17:18           ` Pedro Alves
2008-08-18 17:15       ` Pedro Alves
2008-08-18 18:19         ` Ulrich Weigand

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=20080818162300.GA20375@caradoc.them.org \
    --to=drow@false.org \
    --cc=gdb-patches@sourceware.org \
    --cc=pedro@codesourcery.com \
    --cc=uweigand@de.ibm.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