From: khollan <khollan@daktronics.com>
To: linuxppc-embedded@ozlabs.org
Subject: Re: Debugging with gdbserver slow
Date: Tue, 27 Nov 2007 13:38:31 -0800 (PST) [thread overview]
Message-ID: <13980499.post@talk.nabble.com> (raw)
In-Reply-To: <13865715.post@talk.nabble.com>
Fixed. It turns out it was because I'm using VMWare to run Linux on my
windows computer. I booted up Linux natively and it stepped through code
very fast even in multi threaded apps.
--
View this message in context: http://www.nabble.com/Debugging-with-gdbserver-slow-tf4846374.html#a13980499
Sent from the linuxppc-embedded mailing list archive at Nabble.com.
prev parent reply other threads:[~2007-11-27 21:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-20 20:59 Debugging with gdbserver slow khollan
2007-11-26 15:23 ` khollan
2007-11-27 21:38 ` khollan [this message]
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=13980499.post@talk.nabble.com \
--to=khollan@daktronics.com \
--cc=linuxppc-embedded@ozlabs.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.