Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

Exception Handler Scheme in Security Daemon for OS/2 Platform

IP.com Disclosure Number: IPCOM000117031D
Original Publication Date: 1995-Dec-01
Included in the Prior Art Database: 2005-Mar-31
Document File: 2 page(s) / 52K

Publishing Venue

IBM

Related People

Tran, TM: AUTHOR

Abstract

A method for handling an Exception in Distributed Computing Environment Security Service is disclosed. The Security Service should be able to terminate its threads as well as its process and be able to restart after an Exception occurred.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 59% of the total text.

Exception Handler Scheme in Security Daemon for OS/2 Platform

      A method for handling an Exception in Distributed Computing
Environment Security Service is disclosed.  The Security Service
should be able to terminate its threads as well as its process and be
able to restart after an Exception occurred.

      An Exception occurs as the result of an abnormal condition
during execution.  In C Set/2 compiler, Exceptions are mapped to and
handled as C signals.  The following table lists the C signals that C
Set/2 compiler supports:
  1.  SIGABRT: Abnormal termination signal sent by the ABORT function
  2.  SIGBREAK: Ctrl+Break signal
  3.  SIGFPE: Floating-point exceptions that are not masked
(overflow,
       division by zero, and invalid operation).
  4.  SIGILL: Disallowed instruction
  5.  SIGINT: Ctrl+C signal
  6.  SIGSEGV: Attempt to access an invalid memory
  7.  SIGTERM: Program termination signal sent by the user
  8.  SIGUSR1: User-Defined signal
  9.  SIGUSR2: User-Defined signal
 10.  SIGUSR3: User-Defined signal

      Although an Exception can be caused by different Signals, they
can be handled as a group.  A switch statement in C can be used to
handle this task.  However, the first thing the Exception Handler
routine must do is to check to see whether all the Security Server
interfaces are registered with the RPC runtime and Endpoint Mapper
yet.  To do so, it should check the static BOOLEAN variable named
<register...