callstack trace in c
Debugging means change the software from a behaviuor that has not been requested to one that has been requested. No need for debugging would me you never fail. That I surely do not believe
debugging is localizing, if you got it localized this is just coding
(there is also element of reading / reverse engineering something - something close to debugging*)
* but this (i mean sensoring the unspoiled code) I do yet more rare than debuging - debugging is like fever for programmer - should be avoided
Anyways. Only if you never make a mistake you never must localize. You may minimize the area by only search the last changes. But you must localize. I name it debugging.
this is called compile error not debugging
sometimes it is wrong runtime behavior - but i do not need to localize it - this is not debugging there
real debugging is more rare thing, sometimes i need to do that but this is rare (dont know how often but for sure it is not todays activity maybe not even not one in a whole week (dont rememver) (today i got such damn fatal case. lost whole damn hour on this - but it is not often, and this was becouse i was doing reshaping an larger amount
of code, not normal building up)
Enough of this nonsense. The question has been answered and the thread has gone to hell (again) so I'm closing it.
fir, consider this a warning. Stop demeaning other members of the community when they try to help you, or you can find somewhere else to hang out.
