Debugging plugin load failure

Hi Chris,
When a server/core IO plugin fails to load, MWServer displays “Failure to open XX plugin” and then moves on to any alt objects. Is there any way to get a more verbose error message without building MWServer and loading in a debugger?
Thanks,
M

Hi Mark,

You can get some additional info by launching MWServer from the command line with the environment variable MWORKS_WRITE_MESSAGES_TO_STDERR set to a non-empty value. For example:

$ MWORKS_WRITE_MESSAGES_TO_STDERR=1 /Applications/MWServer.app/Contents/MacOS/MWServer 
Loading CircleStimulusPlugin
Loading DriftingGratingStimulusPlugin
...
NETWORK: Listening socket started at 127.0.0.1 on port 19989

If a plugin fails to load, then the corresponding “Loading …” message should be followed by some information about why the load failed.

Chris