From: Grant Edwards <grante@visi.com>
To: harri.siirtola@vtt.fi
Cc: insight@sources.redhat.com
Subject: Re: Which version with JEENI?
Date: Fri, 01 Nov 2002 11:36:00 -0000 [thread overview]
Message-ID: <20021101133602.A4329@visi.com> (raw)
In-Reply-To: <4.3.2.7.2.20021101110322.00b60100@vttmail.vtt.fi>; from harri.siirtola@vtt.fi on Fri, Nov 01, 2002 at 11:04:45AM +0200
On Fri, Nov 01, 2002 at 11:04:45AM +0200, harri.siirtola@vtt.fi wrote:
> Thanks guys, I think I'll try to install Insight 5.1.1 then.
A few months ago (July) I fixed the RDI target code (which is
used with Jeeni) so that it doesn't suck up all available host
CPU time while the target is executing. If you notice gdb
using a lot of CPU time while it's just sitting there waiting
for your program to hit a breakpoint, that's the bug. A recent
CVS snapshot should have it fixed.
--
Grant Edwards
grante@visi.com
next prev parent reply other threads:[~2002-11-01 19:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-01 1:02 harri.siirtola
2002-11-01 11:36 ` Grant Edwards [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-11-04 3:52 harri.siirtola
2002-11-04 8:20 ` Grant Edwards
2002-10-30 3:44 harri.siirtola
2002-10-30 4:29 ` Masahide Tomita
2002-10-30 4:50 ` Tim Chick
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=20021101133602.A4329@visi.com \
--to=grante@visi.com \
--cc=harri.siirtola@vtt.fi \
--cc=insight@sources.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).