--- Quote Start ---
originally posted by seanbacon@Sep 21 2006, 07:33 AM
most of the breakpoints i put in do not stop the processor (unless i put them in from the "disassembly window). --- Quote End ---
Silly question, do the sources you see in the IDE and the one you use to compile match?
--- Quote Start ---
originally posted by seanbacon@Sep 21 2006, 07:33 AM
also, once the processor is paused, it doesn't single step correctly. also, even though i enabled gdb support for multithread debugging, the ide doesn't show any information on any threads (it just says one thread starting from "no symbol". --- Quote End ---
What connection do you use for debugging? If you use the IDE default way, you debug over an jtag server that connects to the processor debug interface.
Ecos enables an gdb stub, that communictates over a serial line or network with gdb. As I understand this, if you enable multithreading support in ecos the ALTERA debug server doesn't know about it.
You can set breakpoints in the gdb console. In the console view in the title bar there is an icon that lets you switch consoles. You can view download output, stdout, jtag server messages and the standard (comand line) gdb interface. Just open the gdb console and type 'b <my function>' and you set a breakpoint.
Bye,
Wolfgang
Honored Contributor
