Sponsored Content
Operating Systems AIX Is there a way to list all the functions dotted in to the env? Post 302181950 by easwam on Friday 4th of April 2008 02:22:23 PM
Old 04-04-2008
Bug Is there a way to list all the functions dotted in to the env?

Hi People,

Please advise if there is a command to retrieve the list of functions (user-defined) available at any certain point?

Cheers

Last edited by easwam; 04-04-2008 at 03:37 PM..
 

10 More Discussions You Might Find Interesting

1. Post Here to Contact Site Administrators and Moderators

Dotted thread icons

Can you guys please enable the "dotted" icon option, so that the thread icon for a thread in which a user has posted in will appear with a dot in it? Thanks, Aaron (2 Replies)
Discussion started by: Spetnik
2 Replies

2. Shell Programming and Scripting

expanding dotted paths to absolute ones in bash or sh

I have a little script to help me manage a gallery of image files. It makes symbolic links to every file in and below the current directory, placing them in a target directory which is passed to the script as a parameter. Unfortunately, the script pukes when I pass a parameter that contains... (4 Replies)
Discussion started by: TanRanger
4 Replies

3. Solaris

Env

hey guys!!!! i have a few question .. how to modify the user ENV in Sun Solaris 10 ... Thanks!!!! (1 Reply)
Discussion started by: giancarlodjabon
1 Replies

4. Shell Programming and Scripting

Adding command line env in cron env

Hello friends, i run two scripts manually & they work. i run them in cron & they don work. how to match the two env's 1.command line env 2.cron env i would like cron to use command line env. Thanks & Regards Abhijeet (1 Reply)
Discussion started by: abhijeetkul
1 Replies

5. Solaris

OS functions for process list

I'm currently fixing a bug in a C program in which I need to check to make sure another specific application is up and running before continuing. Are there any SunOS API functions that can provide me with a list of currently running processes on the system? I'd like to avoid using 'ps' with a... (1 Reply)
Discussion started by: jalburger
1 Replies

6. Shell Programming and Scripting

Get the List of functions with modified parameters

Hi I have 2 files a.c and a.bak where I changed long to int using awk script. I want to get the list of functions whose parameters got modified for eg: fun ( long a, long b ) might be changed to fun ( int a, int b ) (1 Reply)
Discussion started by: Sivaswami
1 Replies

7. Shell Programming and Scripting

Please explain what code is doing between the two dotted lines

Can someone please explain the meaning of code between the two lines below. if ; then echo "./filter.sh <a flat file containing group and id>" fi ------------------------------------------------------------ >IDnotexist #account in request does not exist in NIS... (1 Reply)
Discussion started by: pinnacle
1 Replies

8. Web Development

Deny from env=env-variable Does not work

(Above from Apache docs). On my system, using: SetEnvIf User-Agent Mozilla IsBad=1 Order allow,deny Allow from all Deny from env=IsBad ...I see that environment variable is set (using phpinfo()) but the page is still served. No errors in the Apache logs. (1 Reply)
Discussion started by: gnurob
1 Replies

9. Shell Programming and Scripting

How to execute functions or initiate functions as command line parameters for below requirement?

I have 7 functions those need to be executed as command line inputs, I tried with below code it’s not executing function. If I run the ./script 2 then fun2 should execute , how to initiate that function I tried case and if else also, how to initiate function from command line if then... (8 Replies)
Discussion started by: saku
8 Replies

10. Shell Programming and Scripting

List of Shell Env Vars

Hia, echo ${!S*} gives me all those env vars starting with S like SHELL SECONDS SHELLOPTS SHLVL etc. is there any way to deflate the shell variables' range like echo ${!A-E*} OR echo ${!A..S*} to list all env vars starting within range of A till E. Thanks Regards, Nasir (1 Reply)
Discussion started by: busyboy
1 Replies
DWARF_GET_TYPES(3)					   BSD Library Functions Manual 					DWARF_GET_TYPES(3)

NAME
dwarf_get_types, dwarf_type_cu_offset, dwarf_type_die_offset, dwarf_type_name_offsets, dwarf_typename -- retrieve information about user- defined types LIBRARY
DWARF Access Library (libdwarf, -ldwarf) SYNOPSIS
#include <libdwarf.h> int dwarf_get_types(Dwarf_Debug dbg, Dwarf_Type **types, Dwarf_Signed *ntypes, Dwarf_Error *err); int dwarf_type_cu_offset(Dwarf_Type type, Dwarf_Off *cu_offset, Dwarf_Error *err); int dwarf_type_die_offset(Dwarf_Type type, Dwarf_Off *die_offset, Dwarf_Error *err); int dwarf_type_name_offsets(Dwarf_Type type, char **name, Dwarf_Off *die_offset, Dwarf_Off *cu_die_offset, Dwarf_Error *err); int dwarf_typename(Dwarf_Type type, char **name, Dwarf_Error *err); DESCRIPTION
These APIs retrieve information about user-defined types from the SGI-specific ``.debug_typenames'' section. Standards-conformant applications should use the functions dwarf_get_pubtypes(3), dwarf_pubtype_cu_offset(3), dwarf_pubtype_die_offset(3), dwarf_pubtype_name_offsets(3) and dwarf_pubtypename(3), which operate on the equivalent ``.debug_pubtypes'' section defined by the DWARF3 standard. Information about user-defined types is returned using opaque descriptors of type Dwarf_Type. Applications need to use the functions described below to retrieve the name and offset information contained in these descriptors. Function dwarf_get_types() retrieves descriptors for all user-defined types associated with the DWARF debug context specified by argument dbg. The argument types should point to a location that will be set to a pointer to an array of Dwarf_Type descriptors. The argument ntypes should point to a location that will be set to the number of descriptors returned. Function dwarf_type_cu_offset() returns the offset, relative to the ``.debug_info'' section, of the compilation unit that contains the debug- ging information entry associated with the argument type. Argument cu_offset should point to a location that will hold the returned offset. Function dwarf_type_die_offset() retrieves the offset, relative to the ``.debug_info'' section, of the debugging information entry associated with the argument type, and stores it into the location pointed to by the argument die_offset. Function dwarf_type_name_offsets() retrieves the name and offsets for the debugging information entry for argument type. Argument name should point to a location which will be set to a pointer to a NUL-terminated string containing the name of the associated debugging informa- tion entry. Argument die_offset should point to a location which will be set to the offset, relative to the ``.debug_info'' section, of the associated debugging information entry. Argument cu_die_offset should point to a location which will be set to a offset, relative to the ``.debug_info'' section, of the first debugging information entry in the compilation unit associated with argument type. Function dwarf_typename() sets the location pointed to by argument name to a pointer to a NUL-terminated string holding the name of the debugging information entry associated with the argument type. Memory Management The memory area used for the array of Dwarf_Type descriptors returned in argument types by function dwarf_get_types() is owned by the DWARF Access Library (libdwarf, -ldwarf). Application code should not attempt to directly free this pointer. Portable code should instead use the function dwarf_types_dealloc(3) to indicate that the memory area may be freed. The memory area used for the string returned in the name argument to functions dwarf_type_name_offsets() and dwarf_typename() is owned by the DWARF Access Library (libdwarf, -ldwarf). Portable code should indicate that the memory area can be freed using the dwarf_dealloc(3) func- tion. Error Returns If argument err is not NULL, these functions will use it to store error information, in case of an error. RETURN VALUES
On success, these functions returns DW_DLV_OK. In case of an error, they return DW_DLV_ERROR and set the argument err. ERRORS
These functions may fail with the following errors: [DW_DLE_ARGUMENT] One of the arguments cu_die_offset, cu_offset, dbg, die_offset, type, types, name, or ntypes was NULL. [DW_DLE_NO_ENTRY] The DWARF debugging context referenced by argument dbg did not contain information about user-defined types. SEE ALSO
dwarf(3), dwarf_get_cu_die_offset_given_cu_header_offset(3), dwarf_get_pubtypes(3), dwarf_pubtype_cu_offset(3), dwarf_pubtype_die_offset(3), dwarf_pubtype_name_offsets(3), dwarf_pubtypename(3), dwarf_types_dealloc(3) BSD
April 10, 2011 BSD
All times are GMT -4. The time now is 02:22 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy