User forums > Embedded development

Can't run debugger

<< < (5/9) > >>

oBFusCATed:
You can try the latest nightly for the debuggers branch and if that doesn't work you've two options:
1. build and debug c::b yourself
2. provide extremely detailed list of steps you're executing, from the compiler installation to the pressing of f8, also I'll need the links to download the compiler and debugger you're using, and a simple test project.

1. will be faster, because I don't like switching to windows too much :)

scarphin:
I'm grateful for ur help. I'm only experienced in C for 8-16 bit microcontrollers and without any experience in C++ so option 1 is not possible by my side, I apologize for that. As for option 2, there exists a list below. ;) That's what I've done for my 3rd try on a 32-bit XP:

1 - I installed codeblocks 10.05 with mingw under 'C:\Program Files\codeblocks' and moved the mingw directory to 'C:\GNU\MinGW' and added 'C:\GNU\MinGW\bin' to PATH
2 - Here is the link for the latest winavr installation
http://sourceforge.net/projects/winavr/files/WinAVR/20100110/WinAVR-20100110-install.exe/download
on the page
http://sourceforge.net/projects/winavr/files/
I installed it under 'C:\GNU\WinAVR' and it adds 'C:\GNU\WinAVR\bin;C:\GNU\WinAVR\utils\bin' to path but I aligned path to make 'C:\GNU\MinGW\bin' come first.
3 - In codeblocks under 'compiler and debugger' settings I corrected compiler's install directory 'C:\GNU\MinGW' for MinGW and 'C:\GNU\WinAVR' for AVR GCC Compiler.
4 - For debugger settings only 'auto-build project to ensure up to date', 'add other open projects paths' and 'do not run debugee' options are not checked.
5 - I attached the project I use to test with the '.cbp' and other files. The project resides in drive 'D:'. It builds without any problems

That's all the changes I made to codeblocks. I think the project options reside in the '.cbp' file if not I'll also list them if needed.

And 1 last thing. I know codeblocks is free and provided 'as is'. I didn't expect for that much help and ur help is much appreciated, thank u! ;)


[attachment deleted by admin]

oBFusCATed:
Why do you add the compilers to the PATH?
Can you try without?
Can you try to misspell the debuggers executable name in the toolchain options?

scarphin:
I add them to path because winavr asks for it and mingw installer also adds it. I tried without compilers in the path, unfortunately same result. When I misspell debugger executable name, codeblocks gives the error 'The debugger executable is not set. To set it, go to...'! There is another detail needs to be told. After nothing happens when I try to run avr debugger with correct executable name, I don't get the error above even I misspell the debugger executable. Nothing changes until I quit and start codeblocks again and then I can get the error above again. It's like codeblocks is waiting for the avr-gdb to start but it never starts and codeblocks debug plugin hangs in the debug state somehow waiting for something. Just my guess.

scarphin:
Ok I've found the problem. In 'Project/Properties' menu under 'Build targets' tab, when u set the type to 'Native' on the 'Selected build target options' which I do for embedded applications, the problem appears. Even when the type is set to 'Native' for the MinGW compiler, the debugger doesn't run like the avr-gdb. Is this the normal behavior for the 'Native' type or should a bug report be filled? Afaik only the linking commands under 'Advanced compiler options' change when the type is changed, don't they?

Navigation

[0] Message Index

[#] Next page

[*] Previous page