[Bug 207079] #include <signal.h> doesn't make ucontext_t available

bugzilla-noreply at freebsd.org bugzilla-noreply at freebsd.org
Fri Feb 12 07:38:37 UTC 2016


https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=207079

--- Comment #6 from commit-hook at freebsd.org ---
A commit references this bug:

Author: kib
Date: Fri Feb 12 07:38:20 UTC 2016
New revision: 295561
URL: https://svnweb.freebsd.org/changeset/base/295561

Log:
  POSIX states that #include <signal.h> shall make both mcontext_t and
  ucontext_t available.  Our code even has XXX comment about this.

  Add a bit of compliance by moving struct __ucontext definition into
  sys/_ucontext.h and including it into signal.h and sys/ucontext.h.

  Several machine/ucontext.h headers were changed to use namespace-safe
  types (like uint64_t->__uint64_t) to not depend on sys/types.h.
  struct __stack_t from sys/signal.h is made always visible in private
  namespace to satisfy sys/_ucontext.h requirements.

  Apparently mips _types.h pollutes global namespace with f_register_t
  type definition.  This commit does not try to fix the issue.

  PR:   207079
  Reported and tested by:       Ting-Wei Lan <lantw44 at gmail.com>
  Sponsored by: The FreeBSD Foundation
  MFC after:    2 weeks

Changes:
  head/include/signal.h
  head/sys/mips/include/ucontext.h
  head/sys/powerpc/include/ucontext.h
  head/sys/sparc64/include/ucontext.h
  head/sys/sys/_ucontext.h
  head/sys/sys/signal.h
  head/sys/sys/ucontext.h
  head/sys/x86/include/ucontext.h

-- 
You are receiving this mail because:
You are the assignee for the bug.


More information about the freebsd-standards mailing list