Sponsored Content
Top Forums Programming Problem with function which reutrns pointer to a value Post 87623 by jim mcnamara on Wednesday 26th of October 2005 11:06:32 AM
Old 10-26-2005
unresolved = fatal error

unresolved means the linker could not find it. The program must have it. The program will not run without it.
 

10 More Discussions You Might Find Interesting

1. Programming

pointer problem

could any one tell why the following is showing segmentation fault while using **ptr but working fine using **a #include<stdio.h> ... (1 Reply)
Discussion started by: useless79
1 Replies

2. Programming

How to return void function pointer

Hello all im trying to build function that will return void function pointer what is mean is ( not working ) the main function void * myClass::getFunction(int type){ if(type==1) return &myClass::Test1; if(type==2) return &myClass::Test2; } void myClass::Test1(){... (1 Reply)
Discussion started by: umen
1 Replies

3. Programming

pass a pointer-to-pointer, or return a pointer?

If one wants to get a start address of a array or a string or a block of memory via a function, there are at least two methods to achieve it: (1) one is to pass a pointer-to-pointer parameter, like: int my_malloc(int size, char **pmem) { *pmem=(char *)malloc(size); if(*pmem==NULL)... (11 Replies)
Discussion started by: aaronwong
11 Replies

4. Programming

Function pointer to inline function ?

Hi. Problem: I have to parse the payload of a packet. The payload could be in Big Endian Format (network byte order) or little. That depends on a flag present in the header of the packet. Solution: A horrible solution could be to check for that flag everytime I have to read a field in the... (11 Replies)
Discussion started by: emitrax
11 Replies

5. Programming

Function Returning Pointer

Hi guys. how a functions such fdopen, ... can return pointer? are these functions use static memory(variables)? (6 Replies)
Discussion started by: majid.merkava
6 Replies

6. Programming

structure pointer array as function parameters

if i create an array of pointers to a structure "struct node" as: struct node *r; and create "n" number of "linked lists" and assign it to the various struct pointers r using some function with a return type as structure pointer as: r=multiplty(.......) /*some parameters*/ is... (2 Replies)
Discussion started by: mscoder
2 Replies

7. Programming

Trivial doubt about C function pointer

Hi, In the below C code, #include <stdio.h> void print() { printf("Hello\n"); } int main() { void (*f)() = (void (*)()) print; f(); (*f)(); } I wonder, how the syntaxes "f()" and "(*f)()" are treated as same without any error? Is this an improvement or ANSI/ISO... (1 Reply)
Discussion started by: royalibrahim
1 Replies

8. Programming

pointer problem

Does anyone know? int x = 1; int *p = &++x; //ok ! int *q = &x++; //gives an error :O why the first pointer is ok but the second is an error? (13 Replies)
Discussion started by: nishrestha
13 Replies

9. Programming

Pure C function pointer on printing vowels twice

Have difficulty to understand this pure C code to only print vowels twice from input string. Questions are commented at the end of each place. #include <stdio.h> #include <stdlib.h> #include <assert.h> #include <limits.h> /* *Demonstrate the use of dispatch tables */ /*Print a char... (11 Replies)
Discussion started by: yifangt
11 Replies

10. Programming

Segmentation fault when I pass a char pointer to a function in C.

I am passing a char* to the function "reverse" and when I execute it with gdb I get: Program received signal SIGSEGV, Segmentation fault. 0x000000000040083b in reverse (s=0x400b2b "hello") at pointersExample.c:72 72 *q = *p; Attached is the source code. I do not understand why... (9 Replies)
Discussion started by: jose_spain
9 Replies
invcutter(1)						      General Commands Manual						      invcutter(1)

Name
       invcutter - generate subset inventory files

Syntax
       /usr/sys/dist/invcutter [ -d ] [ -f root-path ] [ -f version-code ]

Description
       The  command  reads master inventory records from standard input.  A subset inventory record is written to standard output for every record
       read from the input. The information contained in the output record is derived from the input record and the file attribute information	in
       the file hierarchy rooted in the current directory.

Options
       -d		   Enable debugging. No useful diagnostics are printed.

       -f root-path	   Specify an alternate root path for finding file attribute information.

       -v version-code	   Specify a 3-digit version code for use in the version field of the output records. The default version code is 010.

Restrictions
       All input records must be sorted in ascending order on the pathname field.

       Files described in an input record which exist as sockets in the file hierarchy are not processable.

       If a file is described in an input record has a link count greater than 1, all other links to the file must be represented in the input.

Examples
       The following command will generate inventory records for the master inventory entries in PDS020.mi containing version fields set to 020:
	   invcutter -v 020 < PDS020.mi

Return Values
       An exit status of 0 is returned if all goes well. An exit status of 1 is returned if an error occurs. See Diagnostics.

Diagnostics
       "cannot chdir to pathname (error-message)"
       The  program  cannot  change  directories to the pathname directory specified with the -f option. The error-message will provide additional
       information.

       "sort error, record #n"
       The nth input record is not in the correct sort order. All input records must be in ascending  ASCII  colating  sequence  on  the  pathname
       field.

       "cannot stat filename (error-message)"
       An error has occurred attempting to read the attributes of filename.  The error-message explains exactly what happened.

       "pathname: illegal file type code 0140000"
       The file pathname is a socket. Sockets are not supported as valid file types for distribution.

       "unresolved nlink n: pathname"
       This indicates that file pathname in the master inventory is linked to n files which do not appear in the master inventory. Check inventory
       for validity with the program.

       "n unresolved hard links"
       This is an informational message stating how many files were detected in the input inventory which had unresolved links.

See Also
       newinv(1), stl_inv(5), stl_mi(5)
       Guide to Preparing Software for Distribution on ULTRIX Systems

																      invcutter(1)
All times are GMT -4. The time now is 05:13 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy