| Re: [cdt-debug-dev] Cross debugging for embedded target via BDM |
On Wed, 2003-10-01 at 16:43, Leon Pollak wrote: > So, my questions are: > > 1. Where the gdb output goes to? (Why I do not see it in console window?) Best way to trace low level interaction with GDB is to enable a special debug mode. Create a file called options containing the following line. org.eclipse.cdt.debug.mi.core/debug=true Now from the PDE add the following line to the Program arguments: of your development version of Eclipse. -debug file:/home/drt/workspace/options If memory serves correctly all interaction between gdb and eclipse will be output on the console. > 2. How can I increase the Eclipse's time out variable Preferences : C/C++ : Debug : GDB MI : Debugger timeout (ms) > 3. CDT user FAQ suggests fro embedded debugging to use 'remote' target. I > think that this is not applicable in the case of BDM, but may be I am wrong? Assuming your command line interaction looks something like the following ppc-gdb <executable> gdb> target odd-ppc-connection-thing ... gdb> run (or continue) Then the remote target will be of little use to you since gdb's target command is already sorting out your communication. > Many thanks ahead for any help. My pleasure (I am in fact only repeating what I have already found out by asking this list). Finally you may be interested in looking at my plugin to support another embedded target, PalmOS (http://www.redfelineninja.dsl.pipex.com/software.html#eclipse). This is actually an embarrassingly simple package but the plugin is useful/interesting because it requires no changes to the src/xml/anything-else of CDT itself. Cheers Daniel --xx-- -- Daniel Thompson (Merlin) <daniel@xxxxxxxxxxxxxxxxxxxxx> Digitally signed? http://www.redfelineninja.dsl.pipex.com/signature.html If at first you don't succeed then sky diving is probably not for you.
Attachment:
signature.asc
Description: This is a digitally signed message part