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