• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 98 subscribers
  • Views 366 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

ProcMgr_attach with null params error

Elron A Yellin
Expert 1040 points

The docs for syslink (2.10.06.28) ProcMgr_attach() state " If the user does not wish to make any change in the default parameters, the application can simply call ProcMgr_attach() with NULL parameters. The default parameters would get automatically used, " however on linux, I get ProcMgr_E_OSFAILURE.  Using default parameters created with ProcMgr_getAttachParams does work.

  • 0
    TI__Mastermind 22760 points

    Elron,

    There does indeed seem to be a problem with passing NULL for the parameters to ProcMgr_attach().  I will file a bug against SysLink for this.  In the meantime, you can use ProcMgr_getAttachParams() to get the default params to pass to ProcMgr_attach().  Thanks for pointing out this issue.

    Best regards,

        Janet