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, 06 Apr 2005 20:06:00 -0000 [thread overview]
Message-ID: <vt2k6nfu0xd.fsf@zenia.home> (raw)
In-Reply-To: <18aafe4c05040603574ebfbd61@mail.gmail.com>
Vinu Dev <vinudev@gmail.com> writes:
> I Appreciate your contribution to redhat on rda,i have problem using
> rda compilied for FRV target,while debugging thread application using
> rda and gdb compilied for FRV,there is a delay in thread creation when
> compared to creation of thread running the prog on console.
> Can u pls guide me in solving this problem
Is your target system using LinuxThreads, or NPTL?
With LinuxThreads, debugging will slow down your program quite a bit;
there are a lot of signals the thread implementation sends itself
internally, and RDA catches each one. I believe it re-reads the
thread table from the debuggee's memory each time it stops.
The timings your program prints are amazing, though; 38654705694
seconds is around a thousand years. I assume you didn't have to wait
*that* long. How long is the delay?
If you have the option of using NPTL, you might try using RDA from the
jimb-rda-nptl-branch branch. I haven't had time to merge that into
the trunk, but hopefully I'll have some time to work on it eventually.
next prev parent reply other threads:[~2005-04-06 20:06 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 [this message]
2005-04-07 5:01 ` Vinu Dev
2005-04-27 8:47 ` Jim Blandy
[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=vt2k6nfu0xd.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).