From: Hui Zhu <teawater@gmail.com>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb-patches ml <gdb-patches@sourceware.org>
Subject: Re: [RFA]corelow.c: Add tid to add_to_thread_list
Date: Fri, 06 Aug 2010 02:56:00 -0000 [thread overview]
Message-ID: <AANLkTimiQres0-zY_An1bbi5yG9DfNzCc0_jtT2u0P5_@mail.gmail.com> (raw)
In-Reply-To: <m339usx5kc.fsf@fleche.redhat.com>
On Fri, Aug 6, 2010 at 02:44, Tom Tromey <tromey@redhat.com> wrote:
>>>>>> ">" == Hui Zhu <teawater@gmail.com> writes:
>
>>> I make a patch for kernel (http://lkml.org/lkml/2010/8/3/75) but they
>>> think it should be fixed in user space.
>>> So I add the tid to add_to_thread_list.
>
> I don't know about this area of gdb, so I can't really comment on the
> semantics of the change, but I do have a comment about how the change is
> written:
>
>>> - ptid = ptid_build (pid, lwpid, 0);
>>> + tid = 0;
>>> +get_ptid:
>>> + ptid = ptid_build (pid, lwpid, tid);
>>> + if (find_thread_ptid (ptid))
>>> + {
>>> + tid ++;
>>> + goto get_ptid;
>>> + }
>
> I think this would be more readably written without 'goto', as a loop.
>
> Tom
>
Thanks. The prev one is too casual. I make a new one that use the loop.
Best,
Hui
2010-08-06 Hui Zhu <teawater@gmail.com>
* corelow.c(add_to_thread_list): Add tid.
---
corelow.c | 10 ++++++++--
1 file changed, 8 insertions(+), 2 deletions(-)
--- a/corelow.c
+++ b/corelow.c
@@ -244,7 +244,7 @@ add_to_thread_list (bfd *abfd, asection
{
ptid_t ptid;
int core_tid;
- int pid, lwpid;
+ int pid, lwpid, tid;
asection *reg_sect = (asection *) reg_sect_arg;
if (strncmp (bfd_section_name (abfd, asect), ".reg/", 5) != 0)
@@ -278,7 +278,13 @@ add_to_thread_list (bfd *abfd, asection
if (current_inferior ()->pid == 0)
inferior_appeared (current_inferior (), pid);
- ptid = ptid_build (pid, lwpid, 0);
+ tid = 0;
+ do
+ {
+ ptid = ptid_build (pid, lwpid, tid);
+ tid ++;
+ }
+ while (find_thread_ptid (ptid));
add_thread (ptid);
next prev parent reply other threads:[~2010-08-06 2:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-03 8:49 Hui Zhu
2010-08-05 18:44 ` Tom Tromey
2010-08-06 2:56 ` Hui Zhu [this message]
2010-08-06 9:57 ` Pedro Alves
2010-08-06 16:48 ` Hui Zhu
2010-08-06 17:18 ` Pedro Alves
2010-08-06 20:06 ` Pedro Alves
2010-08-06 20:50 ` Maciej W. Rozycki
2010-08-09 2:28 ` Hui Zhu
2010-08-09 14:48 ` 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=AANLkTimiQres0-zY_An1bbi5yG9DfNzCc0_jtT2u0P5_@mail.gmail.com \
--to=teawater@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=tromey@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