A tip I received in the Eclipse CDT forum got me digging in the right direction.
The 0xC0000135 error means "missing component", which may be a driver or DLL.
The basic problem was that, at least with gcc 4.4.0 in place, gdb needs the
system-wide PATH setting (Control Panel -> System -> Advanced -> Environment
Variables) to include at least MinGWin if not even MSYSin (or MSYS>.0in).
That fixed it and the debugging run proceeds as expected to the point where I am
responsible for a crash in my own program, and gdb's diagnosis at that point is
the correct one. I am using a DLL loaded at start time that is independent of
the Windows system DLL, and if that one cannot be found, the same 0xc0000135
Despite the path fix, the original failure symptoms that I reported using gcc
3.4.5 remain unchanged, i.e., my smaller programs went through fine but my large
program exposes an "internal error" in breakpoint.c. What is curious in this
regard is that with 3.4.5, gdb did not require the Windows path modification.
I'm happy to stick with gcc 4.4.0 and will not pursue the 3.4.5 issue further.
Thus, I consider this topic closed.
1629 University Drive
Richardson, TX 75081
Phone: +1 (972) 889-0328