I know there exist already 100 other topics asking for the same problem. I've read them all and couldn't find a solution for my problem.
When I try to debug my c-code it only shows me the assembly.
I'm using Windows 10, 32 bit (win10.jpg)
I've set a breakpoint (breakpoint.jpg)
when i click on go/Debug, it jumps into assembly (assembly.jpg)
I'm using this project options:
compiler Debug Information "Full"
assembler Debug Information "Full" (already tried none)
linker Debug Information "CodeView & COFF format" (already tried "CodeView format" and " COFF format")
when i build the project I got this log output:
"Building HW.exe.
Writing debug information
Compacting CodeView information
Done.
"
soooo. any ideas how to debug in c and not assembler?
What happens with this project?
the same :( it opens the assmebly view
Press once F5. What you see?
the same again (assmebly view)
any other ideas?
hmm ok maybe I have to find a better IDE... or switching back to code::blocks
Quote from: Gurkenwasser on January 06, 2016, 08:53:16 PM
the same again (assmebly view)
any other ideas?
hmm ok maybe I have to find a better IDE... or switching back to code::blocks
You do realize that you are the only one who has that problem, right?
It works just fine for everybody else, so I think it might be better to just find out what you are doing wrong. It might be just a tiny little, subtle thing...
For a new start, try posting your test project, zipped from the project file view, that includes all you project settings and allows to see what is going on.
Just one wild guess is that you have source and executable files in unusual file locations, hence the debugger doesn't find the C source file...
Ralf
Quote from: Bitbeisser on January 06, 2016, 11:00:06 PM
Quote from: Gurkenwasser on January 06, 2016, 08:53:16 PM
the same again (assmebly view)
any other ideas?
hmm ok maybe I have to find a better IDE... or switching back to code::blocks
You do realize that you are the only one who has that problem, right?
It works just fine for everybody else, so I think it might be better to just find out what you are doing wrong. It might be just a tiny little, subtle thing...
For a new start, try posting your test project, zipped from the project file view, that includes all you project settings and allows to see what is going on.
Just one wild guess is that you have source and executable files in unusual file locations, hence the debugger doesn't find the C source file...
Ralf
1. I want apologize if you got me wrong. I don't want hurt the feelings of pelles IDE users... I have no feelings for software, I'm only searching for a new (better) IDE for my C programming lessons. I need an out-of-the-box working IDE without any hassle.
2. yes I've noticed that everyone else could solve this problem. thats the reason why I started a new topic
3. What did you mean with unusual? I tested workspaces on desktop and c root
4. i attached both workspaces
5. I can upload the whole VM if somebody wants to try himself
Check Project option/Compiler/Debug information.
That project was in Desktop folder ???
After some recompiling debugger works normally.
Problem is with Win10 and Desktop.
didn't know that some IDEs can have problems wirth workspaces on desktop (worked for me with visual studio, eclipse and other IDEs).
I tried it again. I created workspaces directly on C:\ and in the documets folder.... without any improvement... so maybe the problem is with windows 10
Quote from: Gurkenwasser on January 07, 2016, 02:43:50 PMI tried it again. I created workspaces directly on C:\ and in the documets folder.... without any improvement... so maybe the problem is with windows 10
Have you checked Project options/Compiler/Debug information...?
@jj2007
It is Windows 10 problem.
Test project works outside special folders ;)
Quote from: jj2007 on January 09, 2016, 04:32:09 AM
Quote from: Gurkenwasser on January 07, 2016, 02:43:50 PMI tried it again. I created workspaces directly on C:\ and in the documets folder.... without any improvement... so maybe the problem is with windows 10
Have you checked Project options/Compiler/Debug information...?
hi,
i've set the settings like in the picture I attached in the second post:
http://forum.pellesc.de/index.php?topic=6864.msg25853#msg25853
(compiler.jpg)
is there something wrong?
Quote from: TimoVJL on January 09, 2016, 11:53:17 AM
@jj2007
It is Windows 10 problem.
Test project works outside special folders ;)
I've tested following folders:
- desktop
- documents
- c:
- d:
- d:\programmierung\c\
nothing worked for me... and I can't really believe that an IDE has problems with paths nowadays... these folders working for any other IDE I've used in the past
Quote from: Gurkenwasser on January 07, 2016, 02:43:50 PM
didn't know that some IDEs can have problems wirth workspaces on desktop (worked for me with visual studio, eclipse and other IDEs).
I tried it again. I created workspaces directly on C:\ and in the documets folder.... without any improvement... so maybe the problem is with windows 10
Well, no, I am running Windows 10/64 Build 11082 on one host and I can debug in source code win Pelle's C 8.00 just fine, see attachment
Ralf
Same problem for me when compiling in 64 bit mode.
When I switched to 32 bit mode it worked ok.
Windows 10/64.