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_SET_REG(3)						       Programming Library						    UNW_SET_REG(3)

NAME

       unw_set_reg -- set register contents

SYNOPSIS

       #include <libunwind.h>

       int unw_set_reg(unw_cursor_t *cp, unw_regnum_t reg, unw_word_t val);

DESCRIPTION

       The unw_set_reg() routine sets the value of register reg in the stack frame identified by cursor cp to the value passed in val.

       The register numbering is target-dependent and described in separate manual pages (e.g., libunwind-ia64(3) for the IA-64 target).  Further-
       more, the exact set of accessible registers may depend on the type of frame that cp is referring to. For ordinary stack frames, it is  nor-
       mally  possible to access only the preserved (``callee-saved'') registers and frame-related registers (such as the stack-pointer). However,
       for signal frames (see unw_is_signal_frame(3)), it is usually possible to access all registers.

       Note that unw_set_reg() can only write the contents of registers whose values fit in a single word. See unw_set_fpreg(3) for a way to write
       registers which do not fit this constraint.

RETURN VALUE

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

THREAD AND SIGNAL SAFETY

       unw_set_reg() is thread-safe as well as safe to use from a signal handler.

ERRORS

       UNW_EUNSPEC
	       An unspecified error occurred.

       UNW_EBADREG
	       An attempt was made to write a register that is either invalid or not accessible in the current frame.

       UNW_EREADONLY
	       An attempt was made to write to a read-only register.

       In  addition,  unw_set_reg()  may  return any error returned by the access_mem(), access_reg(), and access_fpreg() call-backs (see unw_cre-
       ate_addr_space(3)).

SEE ALSO

       libunwind(3), libunwind-ia64(3), unw_get_reg(3), unw_is_signal_frame(3), unw_set_fpreg(3)

AUTHOR

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

Programming Library						  16 August 2007						    UNW_SET_REG(3)
Man Page