From: Mike Wellington <wellington@lucent.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] BDI2000 vs Vision-ICE
Date: Thu, 08 Jan 2004 14:01:59 -0700 [thread overview]
Message-ID: <3FFDC547.3010302@lucent.com> (raw)
In-Reply-To: <3FFD4ECB.8020901@lvl7.com>
People at my place of work are telling me that the
Vision-Ice supports "backtrace" and the BDI2000 does
not. I looked on the Abatron website and it doesn't
say. Can anyone confirm or deny this?
By "backtrace", I mean the ability to set a breakpoint,
hit that breakpoint, and be able to see the last N
instructions executed.
-mike wellington
wellington at lucent.com
John W. Linville wrote:
> Rod Boyce wrote:
>
>> This is just my $0.02 worth but I have used our BDI2000 to debug User
>> land
>> application, Kernel, and device drivers at the same time. It is an
>>
>>
> Rod,
>
> We, too, have used the BDI2000 in such a fashion. I agree that it can
> be invaluable when debugging the interaction between a userland
> application and a kernel driver.
>
> Can you describe the method you use to do this? Our process is a bit
> cumbersome, involving putting a breakpoint in a driver's ioctl()
> function that will only be called by our application. Once it is hit,
> we use add-symbol-file to get the information for our application's
> binary, and we are able to proceed. This is on a PowerPC chip, with the
> special "BDI2000 support" hack turned-on.
>
> Is your method any "cleaner"?
>
> Thanks,
>
> John
>
--
=mike wellington
wellington at lucent.com
303.920.6412 Desk
720.434.7559 Cell
next prev parent reply other threads:[~2004-01-08 21:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-07 18:58 [U-Boot-Users] U-Boot on MPC8280 Rod Boyce
2004-01-08 12:36 ` John W. Linville
2004-01-08 21:01 ` Mike Wellington [this message]
2004-01-08 23:04 ` [U-Boot-Users] BDI2000 vs Vision-ICE Wolfgang Denk
2004-01-09 9:58 ` Richard Danter
-- strict thread matches above, loose matches on Subject: below --
2004-01-08 22:56 Wells, Charles
2004-01-09 13:29 VanBaren, Gerald
2004-01-09 15:50 ` Mike Wellington
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=3FFDC547.3010302@lucent.com \
--to=wellington@lucent.com \
--cc=u-boot@lists.denx.de \
/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