Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

unw_get_proc_name(3) [debian man page]

UNW_GET_PROC_NAME(3)					       Programming Library					      UNW_GET_PROC_NAME(3)

NAME
unw_get_proc_name -- get name of current procedure SYNOPSIS
#include <libunwind.h> int unw_get_proc_name(unw_cursor_t *cp, char *bufp, size_t len, unw_word_t *offp); DESCRIPTION
The unw_get_proc_name() routine returns the name of the procedure that created the stack frame identified by argument cp. The bufp argu- ment is a pointer to a character buffer that is at least len bytes long. This buffer is used to return the name of the procedure. The offp argument is a pointer to a word that is used to return the byte-offset of the instruction-pointer saved in the stack frame identified by cp, relative to the start of the procedure. For example, if procedure foo() starts at address 0x40003000, then invoking unw_get_proc_name() on a stack frame with an instruction-pointer value of 0x40003080 would return a value of 0x80 in the word pointed to by offp (assuming the procedure is at least 0x80 bytes long). Note that on some platforms there is no reliable way to distinguish between procedure names and ordinary labels. Furthermore, if symbol information has been stripped from a program, procedure names may be completely unavailable or may be limited to those exported via a dynamic symbol table. In such cases, unw_get_proc_name() may return the name of a label or a preceeding (nearby) procedure. However, the offset returned through offp is always relative to the returned name, which ensures that the value (address) of the returned name plus the returned offset will always be equal to the instruction-pointer of the stack frame identified by cp. RETURN VALUE
On successful completion, unw_get_proc_name() returns 0. Otherwise the negative value of one of the error-codes below is returned. THREAD AND SIGNAL SAFETY
unw_get_proc_name() is thread-safe. If cursor cp is in the local address-space, this routine is also safe to use from a signal handler. ERRORS
UNW_EUNSPEC An unspecified error occurred. UNW_ENOINFO Libunwind was unable to determine the name of the procedure. UNW_ENOMME The procedure name is too long to fit in the buffer provided. A truncated version of the name has been returned. In addition, unw_get_proc_name() may return any error returned by the access_mem() call-back (see unw_create_addr_space(3)). SEE ALSO
libunwind(3), unw_get_proc_info(3) AUTHOR
David Mosberger-Tang Email: dmosberger@gmail.com WWW: http://www.nongnu.org/libunwind/. Programming Library 16 August 2007 UNW_GET_PROC_NAME(3)

Check Out this Related Man Page

UNW_INIT_REMOTE(3)					       Programming Library						UNW_INIT_REMOTE(3)

NAME
unw_init_remote -- initialize cursor for remote unwinding SYNOPSIS
#include <libunwind.h> int unw_init_remote(unw_cursor_t *c, unw_addr_space_t as, void *arg); DESCRIPTION
The unw_init_remote() routine initializes the unwind cursor pointed to by c for unwinding in the address space identified by as. The as argument can either be set to unw_local_addr_space (local address space) or to an arbitrary address space created with unw_cre- ate_addr_space(). The arg void-pointer tells the address space exactly what entity should be unwound. For example, if unw_local_addr_space is passed in as, then arg needs to be a pointer to a context structure containing the machine-state of the initial stack frame. However, other address-spa- ces may instead expect a process-id, a thread-id, or a pointer to an arbitrary structure which identifies the stack-frame chain to be unwound. In other words, the interpretation of arg is entirely dependent on the address-space in use; libunwind never interprets the argu- ment in any way on its own. Note that unw_init_remote() can be used to initiate unwinding in any process, including the local process in which the unwinder itself is running. However, for local unwinding, it is generally preferable to use unw_init_local() instead, because it is easier to use and because it may perform better. RETURN VALUE
On successful completion, unw_init_remote() returns 0. Otherwise the negative value of one of the error-codes below is returned. THREAD AND SIGNAL SAFETY
unw_init_remote() is thread-safe. If the local address-space is passed in argument as, this routine is also safe to use from a signal han- dler. ERRORS
UNW_EINVAL unw_init_remote() was called in a version of libunwind which supports local unwinding only (this normally happens when defining UNW_LOCAL_ONLY before including <libunwind.h> and then calling unw_init_remote()). UNW_EUNSPEC An unspecified error occurred. UNW_EBADREG A register needed by unw_init_remote() wasn't accessible. SEE ALSO
libunwind(3), unw_create_addr_space(3), unw_init_local(3) AUTHOR
David Mosberger-Tang Email: dmosberger@gmail.com WWW: http://www.nongnu.org/libunwind/. Programming Library 16 August 2007 UNW_INIT_REMOTE(3)
Man Page

Featured Tech Videos