[cdt-debug-dev] Re: Quick Question: Tracing the launch (Mikhail Khodjaia

[Øyvind Harboe <oyvind.harboe@xxxxxxxxx>]

Some more comments:

GDB supports an insane number of CPU's. Quite possibly in the 100's. This makes
it very likely that a CDT + GDB user will be the first to try a particular
combination of CDT + GDB for CPU X. We have developed our own CPU w/GCC+GDB toolchain
here @ Zylin, the ZPU :-)

The new logging feature will help the unworthy figure out why GDB+CDT do
not play together.

These users(often experienced GDB/embedded programmers new to CDT) will succeed in
getting things to work if they can transform the CDT+GDB problem to a GDB only problem.

There are two things that stop them from succeeding in debugging CDT+GDB problems:

- They don't see the communication between CDT & GDB. Being new to Eclipse & 
  CDT, they have absolutely no hope of stumbling accross the right FAQ entry for
  enabling CDT & GDB communication logs.
- Even if they succeed in enabling the logs, they do not realize that the command
  line used to invoke GDB is very different from the command line they normally
  use. They need to be made aware that there is another interpreter in GDB that
  CDT is using. The GUI could implement flashing lights, neon signs, sound 
  alarms, whatever it takes :-)

Once they have the log + the correct GDB command line, they have a "pure GDB" problem,
which they will have a much better chance at dealing with.

Oftentimes it is no more difficult than configuring and building a new
GDB.

-- 
Øyvind Harboe
http://www.zylin.com