Re: [cdt-debug-dev] arm-elf-gcc simulator debugging works with Eclipse

[Amit Aghara <aaghara@xxxxxxxxxx>]

This is a remote debugging issue on a QNX Neutrino RTOS (version 6.2.1)
using Eclipse-CDT. I am just attempting to run and debug a simple hello
world sample.

The error which I get when I run debug on the application it gives me an
error saying "No such file found on target"

My setup details are...
- using Eclipse 2.1 with the latest stable CDT builds from the CVS repos.
- my target RTOS is QNX Neutrino version 6.2.1 with a "ppc" processor which
uses the right level cross-compilers & GDB 5.2.1 under the covers
(ntoppc-gcc & ntoppc-gdb)
- my target is connected to my desktop via ethernet

Here are the steps which I performed based on my reading from few of the
emails on remote debugging...
1) I modified the plugin.xml file under the org.eclipse.debug.mi.core
project. made the following change...
      <debugger
            platform="win32"
            name="%CygwinGDBDebugger.name"
            modes="run,core,attach"
            cpu="native,ppc"                        <--------------------
added "ppc" to the list of cpu's
            class="org.eclipse.cdt.debug.mi.core.CygwinGDBDebugger"
            id="org.eclipse.cdt.debug.mi.core.CygwinCDebugger">
      </debugger>

This change made me get past the problem where I could atleast select a
debugger from my drop-down list in the debug configuraiton page. (Actually
I just ended up adding "ppc" to all the 3 default debuggers
{CygwinGDBDebugger, GDBDebugger & GDBServerDebugger} to be able to try all
options)
2) I created a command file (.gdbinit) with the following commands...
target qnx <ip address of target>:<port>
set qnxremotecwd /<application dir>
sym hello

While debugging thru these plugins, I think it seems that it took the
command file and it attempts to start the GDB process with the following
command....
<specified path to GDB executable>\ntoppc-gdb.exe --cd=<absolute path to yr
project workspace> --command=<specified path to my .gdbinit file>\.gdbinit
-q -nw -i -mi1 <absolute path to the program executable>\hello
for example, C:\qnx\bin\ntoppc-gdb.exe --cd=C:\eclipse\workspace\MyProject
--command=C:\.gdbinit -q -nw -i -mi1 C:\eclipse\workspace\MyProject\hello


Am I missing any more steps to setting this up? or Am I doing something
completely wrong here? I hope I have provided enough info to understand my
problem.

Please advise, I appreciate all yr help. Thanks.

Regards,

Amit Aghara



|---------+------------------------------->
|         |           "Alain Magloire"    |
|         |           <alain@xxxxxxx>     |
|         |           Sent by:            |
|         |           cdt-debug-dev-admin@|
|         |           eclipse.org         |
|         |                               |
|         |                               |
|         |           04/29/2003 05:52 PM |
|         |           Please respond to   |
|         |           cdt-debug-dev       |
|         |                               |
|---------+------------------------------->
  >---------------------------------------------------------------------------------------------------------------|
  |                                                                                                               |
  |       To:       cdt-debug-dev@xxxxxxxxxxx                                                                     |
  |       cc:                                                                                                     |
  |       Subject:  Re: [cdt-debug-dev] arm-elf-gcc simulator debugging works with Eclipse                        |
  |                                                                                                               |
  >---------------------------------------------------------------------------------------------------------------|




>
> Starting with =
> http://dev.eclipse.org/newslists/news.eclipse.tools.cdt/msg01403.html,
> I was able to get the GCC ARM simulator to work.
>
> Neat!
>
> The only trick was that "info threads" causes GDB to crash=20
> before the app is up and running.
>
>
> After some frustrating hours, I figured out a workaround on=20
> gdb.ini as follows:
>
>
> target sim
> #info threads crashes GDB
> load
> break main
> run
> #info threads no longer crashes GDB
>
>
> The workaround is described at the end of this bug-report:
>
> http://bugs.eclipse.org/bugs/show_bug.cgi?id=3D37038
>
>
>
> - I've also fired off a bug-report to the GCC guys
> - I got GCJ compiled code up and running in the Eclipse debugger as =
> well.
>

The crash is gdb related, you should probably send the PR to
the gdb mailing list with the backtrace.

Glad to see things work out.

Can I close the PR 8-)


_______________________________________________
cdt-debug-dev mailing list
cdt-debug-dev@xxxxxxxxxxx
 http://dev.eclipse.org/mailman/listinfo/cdt-debug-dev