Community
Participate
Working Groups
Build Identifier: M20100909-0800 How to set up the executable in embedded environments requires more than just specifying it on the command line. The simplest best(IMHO) solution would be to leave the connection sequence to the user and not require an executable. See problems with PowerPC architecture for instance: http://www.denx.de/wiki/view/DULG/RemoteGPacketReplyIsTooLong Reproducible: Always
Here is the startup script that I use with the Zylin Embedded CDT plugin. Zylin Embedded CDT supports projectless debugging and not specifying a binary. add-symbol-file /home/oyvind/workspace/partech/build/pt_mvci_v1.xx/out/pt_mvci_v100.elf 0 show architecture set architecture powerpc:common target remote 10.0.0.57:2001 Source code for Zylin Embedded CDT: http://repo.or.cz/w/zylincdt.git My goal is to delete as much as possible from Zylin Embedded CDT :-) while still retaining key features like projectless and optional binary launching and complete control of launch process from the GDB init sequence. Cygwin paths are also translated automatically.
Note that there was a way to ignore the executable in the launch, but because that option was obscure, it was removed from the UI in bug 314536. The plumbing is there and we could re-enable it if needed.
