Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [tcf-dev] Antwort: Re: Antwort: Re: Using TCF With Eclipse Debugger

It only takes one company who doesn't see it as a competitive advantage to contribute ARM support and undo that "advantage" for all. In fact, given how prolific ARM is, it would be great community building exercise to have it I would think. Until then, I'm happy using gdb.

Doug.

From: "markus.proeller@xxxxxxx" <markus.proeller@xxxxxxx>
Reply-To: TCF Development <tcf-dev@xxxxxxxxxxx>
Date: Monday, 8 October, 2012 4:53 AM
To: TCF Development <tcf-dev@xxxxxxxxxxx>
Subject: [tcf-dev] Antwort: Re: Antwort: Re: Using TCF With Eclipse Debugger

Hi Eugene,

that means if we use ARM platforms from Xilinx (like zync) we would get a different tcf-agent with debugging support?

Best regards,

Markus



Von:        Eugene Tarassov <eugene.tarassov@xxxxxxxxxx>
An:        TCF Development <tcf-dev@xxxxxxxxxxx>
Datum:        05.10.2012 19:24
Betreff:        Re: [tcf-dev] Antwort: Re:  Using TCF With Eclipse Debugger
Gesendet von:        tcf-dev-bounces@xxxxxxxxxxx




Hi Markus,
 
> What exactly is the reason that ARM debugging is missing in that agent
 
Don’t know about others, my company is not willing to put ARM debugging code to open source at this time, because it is considered to be a competitive advantage.
At same time, contributions from the community are welcome J
 
> … and how much effort would it be to implement that?
 
To support ARM debugging, one needs to implement 3 main components: ARM register descriptors, stack tracing (no symbol info case), and disassembler.
 
Regards,
Eugene
 
From: tcf-dev-bounces@xxxxxxxxxxx [mailto:tcf-dev-bounces@xxxxxxxxxxx] On Behalf Of markus.proeller@xxxxxxx
Sent:
Thursday, October 04, 2012 10:06 PM
To:
TCF Development
Subject:
[tcf-dev] Antwort: Re: Using TCF With Eclipse Debugger

 
Hello Eugene,

we are using the agent from
http://git.eclipse.org/c/tcf/org.eclipse.tcf.agent.git/
What exactly is the reason that ARM debugging is missing in that agent and how much effort would it be to implement that?


Best regards,


Markus




Von:        
Eugene Tarassov <eugene.tarassov@xxxxxxxxxx>
An:        
TCF Development <tcf-dev@xxxxxxxxxxx>
Datum:        
01.10.2012 19:43
Betreff:        
Re: [tcf-dev] Using TCF With Eclipse Debugger
Gesendet von:        
tcf-dev-bounces@xxxxxxxxxxx






Hi Markus,

 
What agent are you using?

ARM debugging support is not available in the open source TCF agent.

 
Regards,

Eugene

 
From:
tcf-dev-bounces@xxxxxxxxxxx [
mailto:tcf-dev-bounces@xxxxxxxxxxx] On Behalf Of markus.proeller@xxxxxxx
Sent:
Monday, October 01, 2012 1:49 AM
To:
tcf-dev@xxxxxxxxxxx
Subject:
[tcf-dev] Using TCF With Eclipse Debugger

 

Hello,


I have a question regarding TCF and the integrated CDT Debugger.

My Eclipse is running on a Windows 7 (64 bit) machine and I have a tcf-agent running on an ARM with Linux.

I'm trying to debug a remote application on the ARM.

In Eclipse under "Debug Configuration" I added a configuration for "Target Communication Framework". I filled out the project name, local file path and remote file path. On the target page I set up the target manually. When I hit the button "Run Tests" I get Connection Diagnostics Errors:


java.lang.Exception: Invalid error report text

      at org.eclipse.tcf.internal.debug.tests.TestEchoERR.doneEchoERR(TestEchoERR.java:107)

      at org.eclipse.tcf.internal.services.remote.DiagnosticsProxy$3.done(DiagnosticsProxy.java:134)

      at org.eclipse.tcf.core.Command.result(Command.java:111)

      at org.eclipse.tcf.core.AbstractChannel.handleInput(AbstractChannel.java:906)

      at org.eclipse.tcf.core.AbstractChannel.access$0(AbstractChannel.java:852)

      at org.eclipse.tcf.core.AbstractChannel$1$1.run(AbstractChannel.java:254)

      at org.eclipse.tcf.EventQueue.run(EventQueue.java:95)

      at java.lang.Thread.run(Unknown Source)


java.lang.Exception: Invalid error report text

      at org.eclipse.tcf.internal.debug.tests.TestEchoERR.doneEchoERR(TestEchoERR.java:107)

      at org.eclipse.tcf.internal.services.remote.DiagnosticsProxy$3.done(DiagnosticsProxy.java:134)

      at org.eclipse.tcf.core.Command.result(Command.java:111)

      at org.eclipse.tcf.core.AbstractChannel.handleInput(AbstractChannel.java:906)

      at org.eclipse.tcf.core.AbstractChannel.access$0(AbstractChannel.java:852)

      at org.eclipse.tcf.core.AbstractChannel$1$1.run(AbstractChannel.java:254)

      at org.eclipse.tcf.EventQueue.run(EventQueue.java:95)

      at java.lang.Thread.run(Unknown Source)


java.lang.Exception: Invalid error report text

      at org.eclipse.tcf.internal.debug.tests.TestEchoERR.doneEchoERR(TestEchoERR.java:107)

      at org.eclipse.tcf.internal.services.remote.DiagnosticsProxy$3.done(DiagnosticsProxy.java:134)

      at org.eclipse.tcf.core.Command.result(Command.java:111)

      at org.eclipse.tcf.core.AbstractChannel.handleInput(AbstractChannel.java:906)

      at org.eclipse.tcf.core.AbstractChannel.access$0(AbstractChannel.java:852)

      at org.eclipse.tcf.core.AbstractChannel$1$1.run(AbstractChannel.java:254)

      at org.eclipse.tcf.EventQueue.run(EventQueue.java:95)

      at java.lang.Thread.run(Unknown Source)


java.lang.Exception: Invalid error report text

      at org.eclipse.tcf.internal.debug.tests.TestEchoERR.doneEchoERR(TestEchoERR.java:107)

      at org.eclipse.tcf.internal.services.remote.DiagnosticsProxy$3.done(DiagnosticsProxy.java:134)

      at org.eclipse.tcf.core.Command.result(Command.java:111)

      at org.eclipse.tcf.core.AbstractChannel.handleInput(AbstractChannel.java:906)

      at org.eclipse.tcf.core.AbstractChannel.access$0(AbstractChannel.java:852)

      at org.eclipse.tcf.core.AbstractChannel$1$1.run(AbstractChannel.java:254)

      at org.eclipse.tcf.EventQueue.run(EventQueue.java:95)

      at java.lang.Thread.run(Unknown Source)



I ignored the errors and hit the Debug button anyway. In the Debug view, I see a new "Debug process" showing up, but nothing else happens. THe name of the Debug process is
remote_debug (imx6: Connecting)


Note: I also used TCF with Remote System Explorer for the same target and I was able to browse the file system and processes.


Best regards,


Markus



This email and any attachments are intended for the sole use of the named recipient(s) and contain(s) confidential information that may be proprietary, privileged or copyrighted under applicable law. If you are not the intended recipient, do not read, copy, or forward this email message or any attachments. Delete this email message and any attachments immediately.

_______________________________________________
tcf-dev mailing list
tcf-dev@xxxxxxxxxxx

http://dev.eclipse.org/mailman/listinfo/tcf-dev



This email and any attachments are intended for the sole use of the named recipient(s) and contain(s) confidential information that may be proprietary, privileged or copyrighted under applicable law. If you are not the intended recipient, do not read, copy, or forward this email message or any attachments. Delete this email message and any attachments immediately.

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


Back to the top