Login or Register to Ask a Question and Join Our Community

Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

unw_get_proc_info_by_ip(3) [debian man page]

UNW_GET_PROC_INFO_BY_IP(3)				       Programming Library					UNW_GET_PROC_INFO_BY_IP(3)

NAME

       unw_get_proc_info_by_ip -- get procedure info by IP

SYNOPSIS

       #include <libunwind.h>

       int unw_get_proc_info_by_ip(unw_addr_space_t as, unw_word_t ip, unw_proc_info_t *pip, void *arg);

DESCRIPTION

       The  unw_get_proc_info_by_ip() routine returns the same kind of auxiliary information about a procedure as unw_get_proc_info(), except that
       the info is looked up by instruction-pointer (IP) instead of a cursor. This is more flexible because it is possible to look up the info for
       an  arbitrary  procedure, even if it is not part of the current call-chain. However, since it is more flexible, it also tends to run slower
       (and often much slower) than unw_get_proc_info().

       The routine expects the followins arguments: as is the address-space in which the instruction-pointer should be looked up.  For	a  look-up
       in  the	local  address-space,  unw_local_addr_space can be passed for this argument.  Argument ip is the instruction-pointer for which the
       procedure info should be looked up and pip is a pointer to a structure of type unw_proc_info_t which is used to return the  info.   Lastly,
       arg is the address-space argument that should be used when accessing the address-space. It has the same purpose as the argument of the same
       name for unw_init_remote().  When accessing the local address-space (first argument is unw_local_addr_space), NULL must be passed for  this
       argument.

       Note  that  for	the  purposes of libunwind, the code of a procedure is assumed to occupy a single, contiguous range of addresses. For this
       reason, it is alwas possible to describe the extent of a procedure with the start_ip and end_ip members. If a  single  function/routine	is
       split into multiple, discontiguous pieces, libunwind will treat each piece as a separate procedure.

RETURN VALUE

       On successful completion, unw_get_proc_info_by_ip() returns 0. Otherwise the negative value of one of the error-codes below is returned.

THREAD AND SIGNAL SAFETY

       unw_get_proc_info()  is	thread-safe.  If  the local address-space is passed in argument as, this routine is also safe to use from a signal
       handler.

ERRORS

       UNW_EUNSPEC
	       An unspecified error occurred.

       UNW_ENOINFO
	       Libunwind was unable to locate unwind-info for the procedure.

       UNW_EBADVERSION
	       The unwind-info for the procedure has version or format that is not understood by libunwind.

       In addition, unw_get_proc_info() may return any error returned by the access_mem() call-back (see unw_create_addr_space(3)).

SEE ALSO

       libunwind(3), unw_create_addr_space(3), unw_get_proc_name(3), unw_get_proc_info(3), unw_init_remote(3)

AUTHOR

       David Mosberger-Tang
       Email: dmosberger@gmail.com
       WWW: http://www.nongnu.org/libunwind/.

Programming Library						  16 August 2007					UNW_GET_PROC_INFO_BY_IP(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