" I worked with a GeForce 8400 gs (quite old) and had a computer with a 32-bit operating system and also the same error is generated"
the 8400/ machine is really a separate case, isn’t it?
perhaps you then also installed a 64 bit cuda with a 32 bit ide
1- if I choose “No” in “Generate GPU Debug Information”, the project works properly, but I can not debug.
2- if I choose “Yes” in “Generate GPU Debug Information”, the project does not work properly, and of course, I can not debug.
if you repeat this experiment for any and all of the cuda samples, i guarantee you that you would each time observe the same outcome, which really should point you towards the setup, not the code/ samples
" when I use Start Debugging CUDA ignores breakpoints in the code positions"
does this sound right?
by default, a correct setup should be able to debug any project, if it passed compilation
moreover, this should again point you towards setup, not code; setup determines the ability of the debugger to function correctly, and not code
i honestly see no causality between user code and a failing debugger; maybe you can explain this to me
cuda as ‘package’ is complex - on linux for instance, it integrates the eclipse ide (generally a stand alone ide), the gnu c compiler and the cuda/ nvidia driver/ libraries, etc
does it rewrite the ide - no, it simply ‘attaches’
does it rewrite the host c compiler - no, it simply ‘attaches’
similarly, for winblows, cuda does not replace the c compiler or ide, it just ‘attaches’
if it ‘attaches’ incorrectly, you are about to witness and experience the kind of problems you now have
and you have to ask yourself whether cuda can attach correctly, if it is 64 bit, and what it attaches to is 32 bit - i doubt; maybe i am wrong
let me ask you a question: if you run a 32 bit ide, can you install a 64 bit plug-in?