Back to index

glibc  2.9
catch-exc.c File Reference
#include <mach/exc_server.h>
#include <hurd/signal.h>
#include <assert.h>

Go to the source code of this file.


kern_return_t _S_catch_exception_raise (mach_port_t port, thread_t thread, task_t task, integer_t exception, integer_t code, integer_t subcode)

Function Documentation

kern_return_t _S_catch_exception_raise ( mach_port_t  port,
thread_t  thread,
task_t  task,
integer_t  exception,
integer_t  code,
integer_t  subcode 

Definition at line 26 of file catch-exc.c.

  struct hurd_sigstate *ss;
  int signo;
  struct hurd_signal_detail d;

  if (task != __mach_task_self ())
    /* The sender wasn't the kernel.  */
    return EPERM;

  d.exc = exception;
  assert (codeCnt >= 2);
  d.exc_code = code[0];
  d.exc_subcode = code[1];
  d.exc_code = code;
  d.exc_subcode = subcode;

  /* Call the machine-dependent function to translate the Mach exception
     codes into a signal number and subcode.  */
  _hurd_exception2signal (&d, &signo);

  /* Find the sigstate structure for the faulting thread.  */
  __mutex_lock (&_hurd_siglock);
  for (ss = _hurd_sigstates; ss != NULL; ss = ss->next)
    if (ss->thread == thread)
  __mutex_unlock (&_hurd_siglock);
  if (ss == NULL)
    ss = _hurd_thread_sigstate (thread); /* Allocate a fresh one.  */

  if (__spin_lock_locked (&ss->lock))
      /* Loser.  The thread faulted with its sigstate lock held.  Its
        sigstate data is now suspect.  So we reset the parts of it which
        could cause trouble for the signal thread.  Anything else
        clobbered therein will just hose this user thread, but it's
        faulting already.

        This is almost certainly a library bug: unless random memory
        clobberation caused the sigstate lock to gratuitously appear held,
        no code should do anything that can fault while holding the
        sigstate lock.  */

      __spin_unlock (&ss->critical_section_lock);
      ss->context = NULL;
      __spin_unlock (&ss->lock);

  /* Post the signal.  */
  _hurd_internal_post_signal (ss, signo, &d,
                           MACH_PORT_NULL, MACH_MSG_TYPE_PORT_SEND,

  return KERN_SUCCESS;

Here is the call graph for this function: