unw_init_remote.man 2.6 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123
  1. '\" t
  2. .\" Manual page created with latex2man on Thu Aug 16 09:44:45 MDT 2007
  3. .\" NOTE: This file is generated, DO NOT EDIT.
  4. .de Vb
  5. .ft CW
  6. .nf
  7. ..
  8. .de Ve
  9. .ft R
  10. .fi
  11. ..
  12. .TH "UNW\\_INIT\\_REMOTE" "3" "16 August 2007" "Programming Library " "Programming Library "
  13. .SH NAME
  14. unw_init_remote
  15. \-\- initialize cursor for remote unwinding
  16. .PP
  17. .SH SYNOPSIS
  18. .PP
  19. #include <libunwind.h>
  20. .br
  21. .PP
  22. int
  23. unw_init_remote(unw_cursor_t *c,
  24. unw_addr_space_t as,
  25. void *arg);
  26. .br
  27. .PP
  28. .SH DESCRIPTION
  29. .PP
  30. The unw_init_remote()
  31. routine initializes the unwind cursor
  32. pointed to by c
  33. for unwinding in the address space identified by
  34. as\&.
  35. The as
  36. argument can either be set to
  37. unw_local_addr_space
  38. (local address space) or to an arbitrary
  39. address space created with unw_create_addr_space().
  40. .PP
  41. The arg
  42. void\-pointer tells the address space exactly what entity
  43. should be unwound. For example, if unw_local_addr_space
  44. is
  45. passed in as,
  46. then arg
  47. needs to be a pointer to a context
  48. structure containing the machine\-state of the initial stack frame.
  49. However, other address\-spaces may instead expect a process\-id, a
  50. thread\-id, or a pointer to an arbitrary structure which identifies the
  51. stack\-frame chain to be unwound. In other words, the interpretation
  52. of arg
  53. is entirely dependent on the address\-space in use;
  54. libunwind
  55. never interprets the argument in any way on its own.
  56. .PP
  57. Note that unw_init_remote()
  58. can be used to initiate unwinding
  59. in \fIany\fP
  60. process, including the local process in which the
  61. unwinder itself is running. However, for local unwinding, it is
  62. generally preferable to use unw_init_local()
  63. instead, because
  64. it is easier to use and because it may perform better.
  65. .PP
  66. .SH RETURN VALUE
  67. .PP
  68. On successful completion, unw_init_remote()
  69. returns 0.
  70. Otherwise the negative value of one of the error\-codes below is
  71. returned.
  72. .PP
  73. .SH THREAD AND SIGNAL SAFETY
  74. .PP
  75. unw_init_remote()
  76. is thread\-safe. If the local address\-space
  77. is passed in argument as,
  78. this routine is also safe to use from
  79. a signal handler.
  80. .PP
  81. .SH ERRORS
  82. .PP
  83. .TP
  84. UNW_EINVAL
  85. unw_init_remote()
  86. was called in a
  87. version of libunwind
  88. which supports local unwinding only
  89. (this normally happens when defining UNW_LOCAL_ONLY
  90. before
  91. including <libunwind.h>
  92. and then calling
  93. unw_init_remote()).
  94. .TP
  95. UNW_EUNSPEC
  96. An unspecified error occurred.
  97. .TP
  98. UNW_EBADREG
  99. A register needed by unw_init_remote()
  100. wasn\&'t accessible.
  101. .PP
  102. .SH SEE ALSO
  103. .PP
  104. libunwind(3),
  105. unw_create_addr_space(3),
  106. unw_init_local(3)
  107. .PP
  108. .SH AUTHOR
  109. .PP
  110. David Mosberger\-Tang
  111. .br
  112. Email: \fBdmosberger@gmail.com\fP
  113. .br
  114. WWW: \fBhttp://www.nongnu.org/libunwind/\fP\&.
  115. .\" NOTE: This file is generated, DO NOT EDIT.