User forums > Embedded development

debugging using codeblocks

<< < (2/2)

anandamu16:

--- Quote ---What is this "if 1"? Have you set a condition on some of your breakpoints?
--- End quote ---
No, I haven't set any condition on breakpoint.


--- Quote ---[debug]> if 1
disassemble 0x00000000
info frame
end
[debug] >
[debug] > >
--- End quote ---
This is the output at debugger log. It occurs whenever I tried to open disassembly window on Codeblocks.
After it, debugger crashes and I need to close gdb from task manager.( as debugger didn't closed from codeblocks toolbar icons)

yvesdm3000:
That "if 1" seems to be coming from GdbCmd_DisassemblyInit so i assume the version of arm-none-eabi-gdb.exe might not be completely compatible with CodeBlocks' gdb support.

Yves

anandamu16:
Hey Thanks.
 Previously I was using "C:\Program Files (x86)\GNU Tools ARM Embedded\6.2 2016q4\bin\arm-none-eabi-gdb.exe", Disassembly window was crashing up. On using"C:\Program Files (x86)\GNU Tools ARM Embedded\5.4 2016q3\bin\arm-none-eabi-gdb.exe", Disassembly window works fine.

Any idea, why it was not supporting disassembly previously? Moreover If you know which is the stable release of arm-none-eabi-gdb to be worked with codeblocks?

yvesdm3000:
Sorry I don't have experience with that toolset or compiler. I just looked up and examined the code that generated that "if 1" statement and saw that there is possibly a communication-error between codeblocks and that gdb.exe application.

I hope you understand that there is no army of developers following up every version of gdb and fix that for codeblocks...

Yves

Navigation

[0] Message Index

[*] Previous page