Debugging plugin load failure

mhisted's Avatar

mhisted

28 Apr, 2014 06:50 PM

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

  1. Support Staff 1 Posted by Christopher Sta... on 28 Apr, 2014 06:59 PM

    Christopher Stawarz's Avatar

    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

  2. Christopher Stawarz closed this discussion on 30 Apr, 2014 01:54 PM.

Comments are currently closed for this discussion. You can start a new one.

Keyboard shortcuts

Generic

? Show this help
ESC Blurs the current field

Comment Form

r Focus the comment reply box
^ + ↩ Submit the comment

You can use Command ⌘ instead of Control ^ on Mac