views:

50

answers:

0

Hi everyone,

I'm using Eclipse CDT with Zylin embedded debug (native) and arm-elf-gdb 6.6 on OS X 10.5.8. I've got an OCD debugger connecting to a board with an ARM processor.

Eclipse is able to stop at the first breakpoint and gather variables from memory, but any subsequent breakpoints or single-steps fail. I can set breakpoints ok when using commandline gdb, but setting breakpoints at the exact same location gives me these errors in Eclipse:

Warning:
Cannot insert breakpoint 2.
Error accessing memory address 0x3f6: Unknown error: -1.

And my OCD connection dies with "Error: unexpected error -308"

I'm using the same OCD script in both cases.

The only differences I see are (1) Eclipse uses Zylin and the mi protocol to talk to gdb, and (2) my gdb script is invoked differently in this way:

When running from gdb, I use a script file that ends with these two lines:

load        filename.out
symbol-file filename.out

In Eclipse, I copy the contents of this script file into "Debug Configurations | Commands" (I've tried both the "'Initialize' Commands" and "'Run' Commands" boxes. I replace the last two lines with load, and specify filename.out in the "Debug Configurations | Main | C/C++ Application" box.

I'd appreciate any suggestions about how to get Zylin+Eclipse to behave. Thanks.