From: Jim Blandy <jimb@redhat.com>
To: Vinu Dev <vinudev@gmail.com>
Cc: rda@sources.redhat.com
Subject: Re: Help required on rda [FRV]
Date: Wed, 27 Apr 2005 08:47:00 -0000 [thread overview]
Message-ID: <vt2zmvkfw1c.fsf@zenia.home> (raw)
In-Reply-To: <18aafe4c05040622017bc4ed22@mail.gmail.com>
Vinu Dev <vinudev@gmail.com> writes:
> Dear JimB,
> Thanks for your reply,iam using LinuxThreads,its my requirement to
> use linuxthreads.
> Even i was surprised by the delay factor,is there any other way to
> measure the thread creation time more precise than using
> gettimeofday() system call,if u could advice me on this,i would be
> very much thankfull to you.
> The delay is around 4-5 secs for each thread creation via rda.
> Is there any article or technical documents or could u guide me to
> know the cause for this delay?
4-5 seconds sounds about right. If I remember correctly, it's due to
libthread_db's need to read huge amounts of memory from the program
being debugged each time it stops.
Take a look at rda/unix/linux-target.c:linux_process_rcmd. That's the
function that gets called when you give GDB the "monitor" command. So
(gdb) monitor 1
(I think) should turn on debugging output in RDA, and
(gdb) monitor 0
should turn it off. If you'd like to be able to do other things to
RDA, you can add more stuff to linux_process_rcmd.
In any case, after 'monitor 1', RDA will print messages describing
all the ptrace calls it makes. If I'm right, you'll see a *lot* of
ptrace traffic during those 4-5 seconds.
You might also try changing the initialization of thread_db_noisy to
1, to see more of what thread_db.c is doing.
Good luck!
next prev parent reply other threads:[~2005-04-27 8:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-06 10:58 Vinu Dev
2005-04-06 20:06 ` Jim Blandy
2005-04-07 5:01 ` Vinu Dev
2005-04-27 8:47 ` Jim Blandy [this message]
[not found] ` <18aafe4c05042803374d2b517b@mail.gmail.com>
2005-05-16 4:20 ` Vinu Dev
2005-05-16 21:14 ` Jim Blandy
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=vt2zmvkfw1c.fsf@zenia.home \
--to=jimb@redhat.com \
--cc=rda@sources.redhat.com \
--cc=vinudev@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).