yeah, that's why I found it easier to just write out a .so with my own makefile, before invoking the sdk's build script for it (side note: msvc can invoke makefiles from the ide, if you want to go that route, just tell it to use gmake from msys/cygwin/etc instead of nmake).
yeah, you need some separate eclipse project in order to then debug it, but meh, printfs and logcat get the job done too. you can get stack traces from adb/logcat too.
if you can run the same code on windows/linux and get proper stack traces for crashes there instead, then its just much simpler that way instead of trying to get the user to figure out how to use a shell/adb/logcat stuff.
I guess its just personal preference: msvc > vim+make+stacktraces > everything else. saves having to deal with other UIs.
incidentilly, if you're trying to crash FTE, please do it with this build - http://triptohell.info/moodles/win32/debug/fteglqw.exe
- because it'll give you a stack trace that I can then try to use to find+fix the crash.
regarding HLBSP, the standard valve tools have usage restrictions upon them that limit their use in non-halflife engines - ie: they cannot be used. my memory is hazy, so be sure to read it properly.