From my experience at tri-Ace, there are no Android NDK (C++) debuggers that work on all devices, only for a limited set of them.And according to the 2nd link you posted, you have to use quite a retarded hack to get breakpoints to work, assuming the device is supported in the first place.L. Spiro
Not sure what to tell you here, other than that it works.
At work I have personally debugged a large C++ library on ten or so devices, mostly Asus, Samsung, Sony, LG and Motorola, without issue. I an aware that other engineers have debugged on other devices, including from smaller international Android handset manufacturers.
We have a compatibility spreadsheet which indicates successful testing of both our library and development environment on 60 or so devices. All of these devices are Gingerbread or above; possibly prior to this support was less mature.
I am sympathetic to you scepticism but in reality I've found support for debugging effectively ubiquitous.
As for the "retarded hack", it is true that gdb takes a few seconds to attach. If debugging some user controlled event this is not an issue. If debugging application startup it is sometimes necessary to include an artificial delay (i.e., sleep(5) or similar). Not too onerous but yes, somewhat irritating.