From: "Ulrich Weigand" <uweigand@de.ibm.com>
To: xdje42@gmail.com (Doug Evans)
Cc: palves@redhat.com (Pedro Alves), gdb-patches@sourceware.org
Subject: Re: Cell multi-arch broken (Re: [PATCH 2/2] GNU/Linux: Stop using libthread_db/td_ta_thr_iter)
Date: Fri, 28 Aug 2015 13:11:00 -0000 [thread overview]
Message-ID: <20150828131056.2352E8775@oc7340732750.ibm.com> (raw)
In-Reply-To: <m34mjkexxd.fsf@sspiff.org> from "Doug Evans" at Aug 27, 2015 11:20:46 PM
Doug Evans wrote:
> One might ask "Why doesn't thread_from_lwp just return thread_info?"
Yes, I did ask myself that too :-)
> 2015-08-27 Doug Evans <xdje42@gmail.com>
>
> * linux-thread-db.c (record_thread): Return the created thread.
> (thread_from_lwp): Likewise.
> (thread_db_get_thread_local_address): Update.
Makes sense to me.
Thanks,
Ulrich
--
Dr. Ulrich Weigand
GNU/Linux compilers and toolchain
Ulrich.Weigand@de.ibm.com
next prev parent reply other threads:[~2015-08-28 13:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-08 19:11 [PATCH 0/2] GNU/Linux: Stop using libthread_db/td_ta_thr_iter Pedro Alves
2015-02-08 19:11 ` [PATCH 1/2] linux-nat.c: fix a few lin_lwp_attach_lwp issues Pedro Alves
2015-02-08 19:11 ` [PATCH 2/2] GNU/Linux: Stop using libthread_db/td_ta_thr_iter Pedro Alves
2015-08-26 17:39 ` Cell multi-arch broken (Re: [PATCH 2/2] GNU/Linux: Stop using libthread_db/td_ta_thr_iter) Ulrich Weigand
2015-08-26 18:23 ` Pedro Alves
2015-08-26 19:02 ` Ulrich Weigand
2015-08-26 19:42 ` Pedro Alves
2015-08-27 17:40 ` Ulrich Weigand
2015-08-28 6:21 ` Doug Evans
2015-08-28 13:11 ` Ulrich Weigand [this message]
2015-09-08 10:31 ` Pedro Alves
2015-09-19 6:21 ` Doug Evans
2015-02-20 21:46 ` [PATCH 0/2] GNU/Linux: Stop using libthread_db/td_ta_thr_iter 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=20150828131056.2352E8775@oc7340732750.ibm.com \
--to=uweigand@de.ibm.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.com \
--cc=xdje42@gmail.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