|
| Re: Cross debugging [message #32758 is a reply to message #32655] |
Fri, 06 March 2009 18:51   |
 Martin Oberhuber
Messages: 1007
Registered: July 2009 |
Senior Member |
|
|
Hi Phil,
I guess you'll need to post this question on the
eclipse.tools.cdt
newsgroup, or mail to the cdt-dev mailing list ... since it's
actually cdt specific.
Thanks,
--
Martin Oberhuber, Senior Member of Technical Staff, Wind River
Target Management Project Lead, DSDP PMC Member
http://www.eclipse.org/dsdp/tm
Phil Longstaff wrote:
> I have compiled a copy of gdb 6.8 as a cross-debugger from linux/i86 to
> linux/ppc for an embedded target. If I install CDT and RSE, I can set
> up a connection to the target and remote launch configuration. I can
> then change the command from 'gdb' to '/to/path/my-cross-gdb' and set up
> the solib path to match the cross-built libraries, and can do successful
> debugging on the target.
>
> I'm now trying to package this up into a plugin which will automatically
> set the command and path correctly. My plugin has an extension to the
> CDebugger and CDebuggerPage extension points, but I don't see my
> debugger in the drop down in the remote c++ launch configuration
> dialog. Ideally, I'd like my debugger to be the default if the remote
> target type is linux/ppc, but don't see remote platform cpu in the
> connection parameters.
>
> I don't know what I'm missing.
>
> Phil
>
|
|
|
| Re: Cross debugging [message #579504 is a reply to message #32655] |
Fri, 06 March 2009 18:51 |
Martin Oberhuber
Messages: 1007
Registered: July 2009 |
Senior Member |
|
|
Hi Phil,
I guess you'll need to post this question on the
eclipse.tools.cdt
newsgroup, or mail to the cdt-dev mailing list ... since it's
actually cdt specific.
Thanks,
--
Martin Oberhuber, Senior Member of Technical Staff, Wind River
Target Management Project Lead, DSDP PMC Member
http://www.eclipse.org/dsdp/tm
Phil Longstaff wrote:
> I have compiled a copy of gdb 6.8 as a cross-debugger from linux/i86 to
> linux/ppc for an embedded target. If I install CDT and RSE, I can set
> up a connection to the target and remote launch configuration. I can
> then change the command from 'gdb' to '/to/path/my-cross-gdb' and set up
> the solib path to match the cross-built libraries, and can do successful
> debugging on the target.
>
> I'm now trying to package this up into a plugin which will automatically
> set the command and path correctly. My plugin has an extension to the
> CDebugger and CDebuggerPage extension points, but I don't see my
> debugger in the drop down in the remote c++ launch configuration
> dialog. Ideally, I'd like my debugger to be the default if the remote
> target type is linux/ppc, but don't see remote platform cpu in the
> connection parameters.
>
> I don't know what I'm missing.
>
> Phil
>
|
|
|
|
Powered by
FUDForum. Page generated in 0.03543 seconds
] 
Search
Help
Register
Login
Home
