From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mike Wellington Date: Thu, 08 Jan 2004 14:01:59 -0700 Subject: [U-Boot-Users] BDI2000 vs Vision-ICE In-Reply-To: <3FFD4ECB.8020901@lvl7.com> References: <3FFD4ECB.8020901@lvl7.com> Message-ID: <3FFDC547.3010302@lucent.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de 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