FYI Watcom C++ 11.0b's debugger does not work on OS/2 WSeB.  There is
something wrong with the startup code generated by the compiler so that
a task exception (general protection fault) happens before the debugger
gets to the startup code (even before it goes to main()).  It looks like
it might be failing either in the debugger or in some .DLL's
initialization.  The only way to get an EXE to load into WD is to either
get rid of the .SYM file (no symbols makes for tough debugging) or use
"Debug Startup" but that traps before it gets to the start of your code.

If anyone else if affected by this, I would recommend you get to
Watcom's website, newsgroups and if your stomach can take it, tech
support ASAP since powersoft is wrapping up Watcom C++ support.

Rob.
___
 X SLMR 2.1a X Summer is half the clothing, twice the fun!

--- Maximus/2 3.01