From: Bhavana Babu
[mailto:bhavana.babu@xxxxxxxxxxxxx]
Sent: Monday, March 15, 2010 12:35 AM
To: CDT General developers list.
Subject: RE: [cdt-dev] Debugging with EDC
>As it is, without an
ARM-specific launch delegate, you probably selected the "EDC Create
Process (Windows)" launcher. That says to use Windows as the >debug
target. So this is failing because Win32 can't run ELF. (Or, ARM
code, for that matter. ;)
>Again, this kind of support is
imminently possible, but not on our schedule right now. If you're
interested and want to work on it, we can help!
Hi Ed,
Thanks
for the reply….
But I
have tried this with an exe build with cygwin/Mingw .
Thus I
got the following display on editor:
No
source is available while stepping. Can anyone tell me what is happening ?
From: cdt-dev-bounces@xxxxxxxxxxx
[mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Ed.Swartz@xxxxxxxxx
Sent: Friday, March 12, 2010 7:37 PM
To: cdt-dev@xxxxxxxxxxx
Subject: RE: [cdt-dev] Debugging with EDC
Hi Bhavana,
> Can anyone tell me whether
remote debugging is supported using EDC?
> We
want to debug the code running in ARM target using gdbServer.
> Can
anyone tell me how this is possible using EDC?
> Any
help will be appreciated.
This case is theoretically
supported, since EDC is built on TCF and inherently supports remote
debugging. And, we have ARM support and gdbserver support.
But as of yet, we've only tested
ARM on Symbian using the TRK protocol and gdbserver on a Linux/x86 local
system. We haven't yet done the gdbserver ARM
targeting pieces or tested a gdbserver/ARM combination.
And the gdbserver support has only been tested on the local system so far and
is bundled as a JAR.
To get this working, we'd need to
handle, e.g., copying/mapping files to the remote system, launching the
gdbserver agent remotely (and maybe changing it from a JAR file to a C/C++
agent), wiring up the gdbserver agent with the ARM targeting pieces, etc.
> I have imported a sample elf
program( build for ARM ,using arm-none-eabi-gcc) through “Import-àC/C++ Executable” option in Eclipse
3.6M5.
> Then I tried to debug it
using ” EDC create process Launcher”, selected Win32 Debug Agent(TCP
10.1.11.75:1534(local running)) as TCF peer.
> But I got the following error
:
As it is, without an ARM-specific
launch delegate, you probably selected the "EDC Create Process
(Windows)" launcher. That says to use Windows as the debug target.
So this is failing because Win32 can't run ELF. (Or, ARM code, for that
matter. ;)
Again, this kind of support is
imminently possible, but not on our schedule right now. If you're
interested and want to work on it, we can help!
-- Ed
From: Bhavana Babu
[mailto:bhavana.babu@xxxxxxxxxxxxx]
Sent: Friday, March 12, 2010 4:08 AM
To: cdt-dev@xxxxxxxxxxx
Subject: [cdt-dev] Debugging with EDC
Hi all,
I have imported a sample elf
program( build for ARM ,using arm-none-eabi-gcc) through “Import-àC/C++ Executable” option in Eclipse
3.6M5.
Then I tried to debug it using ”
EDC create process Launcher”, selected Win32 Debug Agent(TCP
10.1.11.75:1534(local running)) as TCF peer.
But I got the following error :
Error in final launch sequence.
org.eclipse.core.runtime.CoreException: TCF error report:
Command: Processes start "", "C:\\Simple.elf",
["C:\\Simple.elf"], ["USERPROFILE=...
Time: 2010-03-12 14:58:55.415
Error text: Unknown error
Error code: 1
Alt code: 193
Alt org: POSIX
Can anyone help me…
Thanks in advance ,
Bhavana