[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
RE: [cdt-dev] Zylin CDT problem for ppc platform
|
Thank you for your help. I will examine them with my team.
When I've searched web about CDT, I found some information which states that
we should change cpu to ppc as given below:
Is it necessary to cross-debug?
1) Cross-Debug Workaround for the GDB/MI interface. (Found
in the Eclipse news groups.)
In file plugins/org.eclipse.cdt.debug.mi.core_1.0.0/plugin.xml
change the lines
cpu="native"
into
cpu="native,mycpu1,mycpu2"
or
cpu="*"
where mycpu1, mycpu2, ... are the cpu names used by GDB, e.g.
"arm,i386,..."
Thank you,
Kind regards,
Cagatay Catal
-----Original Message-----
From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On
Behalf Of Chris Recoskie
Sent: 12 November 2006 04:11
To: CDT General developers list.
Subject: RE: [cdt-dev] Zylin CDT problem for ppc platform
There can be a lot of things at work if you are having problems running out
of breakpoints...
- Is the "go to main" temporary breakpoint being cleared properly once it
is hit? (usually fine but you never know)
- Are you consuming a breakpoint to support console I/O? (printf etc.).
- Are you consuming a breakpoint for the end of the program?
In a former life, the team I was working on had to contend with a lot of
such issues. The microcontroller we were supporting has no software trap
instruction, and some devices had as few as one hardware breakpoint. As a
result we ended up with a lot of non-standard options in our GDB port to
support disabling any un-needed sources of breakpoint usage. And yes,
supporting what appeared to be a limitless supply of breakpoints in the IDE
when you have no TRAP and one HW breakpoint is a real pain :-P
===========================
Chris Recoskie
Team Lead, IBM CDT Team
IBM Toronto
http://www.eclipse.org/cdt
"Mikhail
Khodjaiants"
<Mikhail.Khodjaia To
nts@xxxxxxx> "CDT General developers list."
Sent by: <cdt-dev@xxxxxxxxxxx>
cdt-dev-bounces@e cc
clipse.org
Subject
RE: [cdt-dev] Zylin CDT problem
10/11/2006 09:14 for ppc platform
AM
Please respond to
"CDT General
developers list."
<cdt-dev@eclipse.
org>
The CDT debugger uses the gdb command "next" for stepping, it doesn't set
hardware breakpoints explicitly. I would suggest to use the verbose console
mode to find out what is happening in your case.
From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On
Behalf Of Çagatay Çatal
Sent: 10 November 2006 13:22
To: 'CDT General developers list.'
Subject: [cdt-dev] Zylin CDT problem for ppc platform
Hi,
In these days my colleagues in my project team try to use Zylin CDT for ppc
processor to debug u-boot in a remote fashion.
It works fine for arm according to some documents on web but we did not
succeed to work for ppc.
We get an error and this error is same when we put 2 hardware breakpoints
for DDD. Normally we can only
use 1 hardware breakpoint for ppc but arm9 has 2 hardware breakpoints.
ppc processors have only 1 hardware breakpoint but if Zylin or CDT uses
more than 1 hardware breakpoints,
we get such an error.
We successfuly debug u-boot using GDB/DDD but we can not do it with CDT.
My colleagues want to use Eclipse and CDT project for this purpose but now,
we can't.
Will there any improvement for this purpose in new versions of CDT? Such an
improvement would simplify embedded developers' workings with the great
support of CDT.
Is it true that CDT uses more than 1 hardware breakpoints for stepping? A
colleague of me thinks that CDT uses more than 1 and this is the reason of
failure.
If someone has succeeded to use ZylinCDT or CDT for ppc with this purpose,
please let me know.
Thank you,
Best wishes,
******************************************
Cagatay Catal
MSc Computer Engineer
TUBITAK-Marmara Research Center
Information Technology Institute
Gebze, Kocaeli - TURKEY
******************************************
--
IMPORTANT NOTICE: The contents of this email and any attachments are
confidential and may also be privileged. If you are not the intended
recipient, please notify the sender immediately and do not disclose the
contents to any other person, use it for any purpose, or store or copy the
information in any medium. Thank you.
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev
