[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [cdt-debug-dev] Breakpoints broken in CDT CVS HEAD w/CygWin GDB for ARM
|
The CygWin hosted GDB crashes when it is fed Windows paths.
I am using CygWin hosted gdb (for x86) and it doesn't crash.
BTW, whats happening w.r.t. CDT supporting GDB not running under the
same host as CDT?
The binaries are built on Windows (within or without CygWin) and the debug
information contains host paths. When youn set a breakpoint gdb uses these
paths combimed with the source search path to find the source file. The
problem is CygWin paths. We are looking for solution, but for now you can
try to add a mapping source container that maps </cygdrive/c> to <c:/>. This
should work fine if your executable contains CygWin paths.
My #1 wish for CDT is still generic first class projectless GDB
debugging GUI, i.e. an Insight killer :-)
We are trying to do our best ...
----- Original Message -----
From: "Øyvind Harboe" <oyvind.harboe@xxxxxxxxx>
To: <cdt-debug-dev@xxxxxxxxxxx>
Sent: Thursday, May 05, 2005 12:54 PM
Subject: [cdt-debug-dev] Breakpoints broken in CDT CVS HEAD w/CygWin GDB for
ARM
Breakpoints seem to work fine. It's gdb that is not responding.
OK.
The problem is that with the latest CDT, more Windows paths are being
handed to a CygWin hosted GDB. The CygWin hosted GDB crashes when it is
fed Windows paths.
BTW, whats happening w.r.t. CDT supporting GDB not running under the
same host as CDT?
The most important aspect being path handling.
I consider Windows and CygWin different types of hosts in this context.
BTW, there is a new Eclipse-based open source project - Device
Software
Development Platform (DSDP). They have just posted the proposals in
the news
group (eclipse.dsdp). I think you might be interested in it.
For me this changes very little unless it translates into resources
being poured into improving the CDT GDB GUI. It's an excellent piece of
software, but much remains to be done.
For embedded development, I don't particularly miss any features beyond
what the Zylin Embedded CDT Plugin provides.
I'm not all hot and bothered about an Eclipse GUI that programs flash or
otherwise interacts with the target embedded device. Also, I'd hate to
see resources that could be poured into an improved CDT GDB GUI being
diverted.
My #1 wish for CDT is still generic first class projectless GDB
debugging GUI, i.e. an Insight killer :-)
--
Øyvind Harboe
http://www.zylin.com
_______________________________________________
cdt-debug-dev mailing list
cdt-debug-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-debug-dev
