DosSetSigHandler API Not Behaving as Expected in OS/2 Subsystem

 Last reviewed: March 24, 1997
Article ID: Q154963
The information in this article applies to:
  • Microsoft Windows NT Workstation version 3.51
  • Microsoft Windows NT Server version 3.51

SYMPTOMS

The DosSetSigHandler API does not behave as it should in the Windows NT OS/2 SubSystem when called with a NULL Handler and SIGA_IGNORE, as in the following example: 

   DosSetSigHandler(NULL,..,SIGA_IGNORE)

CAUSE

In the OS/2 Subsystem a macro was generating an incorrect address in the case where a null handler value was passed in as a parameter.

RESOLUTION

Apply the fix mentioned below. The solution was to recognize the null value and flag the IGNORE parameter. This is the expected behavior for DosSetSigHandler handling in this case.

STATUS

This problem was corrected in the latest Windows NT 3.51 U.S. Service Pack. For information on obtaining the Service Pack, query on the following word in the Microsoft Knowledge Base (without the spaces):

S E R V P A C K

Additional query words: prodnt OS2
Keywords : kbbug3.51 kbfix3.51.sp5 kbnetwork ntnetserv
Version : 3.51
Platform : WinNT

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: March 24, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.