07-29-2011
Hi.
How is my use of iargc in the example "f1" different from your use of iargc? ... cheers, drl
10 More Discussions You Might Find Interesting
1. Solaris
I am compiling a software named wine
When i run make then at the end following error generated.
DVAPI32_ -foversion.res version.rc
ld.so.1: ../../tools/wrc/wrc: fatal: relocation error: file ../../tools/wrc/wrc: symbol wine_casemap_upper: referenced symbol not found
*** Signal 9
make:... (0 Replies)
Discussion started by: mansoorulhaq
0 Replies
2. Programming
i have a class name 1.c in tht i am using function n wich has his body in 2.c and declaration in 2.h
now how can i compile 1.c.
ex;
1.c
int main()
{
//some data
n(10);
//somedata
}
*****
2.c
int n(int k)
{
//some data
}
int main()
{
some data (2 Replies)
Discussion started by: phani_sree
2 Replies
3. Programming
Hi,
Environment : HP-UX avalon B.11.11 U 9000/800 3547052374 unlimited-user license
aCC version :aCC: HP ANSI C++ B3910B A.03.37
I need to find a way out of this errors.can anyone help me .
$ aCC db.cc -I$ORACLE_HOME/rdbms/public -I/disk1/oracle/product/10.2.0.2/*
Error (future)... (1 Reply)
Discussion started by: varuntayur
1 Replies
4. AIX
Hi,
I have AIX 5.3 and my code is written in proc . i am getting following error during compilation
Please help?////.....
[H[2J:-d:
Compiling with RMS
cc -w -q32 -qidirfirst -ISource/Header -I/usr/vacpp/include -q32 -DRMS -DDISEC -DDBG -DBIGENDIAN -DBIT32 -c -q32... (0 Replies)
Discussion started by: ajaysahoo
0 Replies
5. AIX
hi, I first want to apologize for my poor english !
I'm a newbe on Unix system and I have to install NRPE on an AIX 5.3.
I have downloaded the NRPE Source code and i need to compile them...
the problem is, when I do a:
./configure --enable-command-args --disable-ssl
it returns me :... (1 Reply)
Discussion started by: Cyr1us
1 Replies
6. Programming
Dear all
I am new to C programming
In response to the post
cat get_time.c
#include <stdlib.h>
#include <sys/time.h>
main()
{
struct timeval tv;
struct timezone tz;
struct tm *tm;
gettimeofday(&tv, &tz);
tm=localtime(&tv.tv_sec);
printf("... (2 Replies)
Discussion started by: on9west
2 Replies
7. AIX
Hi,
I am executing the below mentioned code:-
proc SQLCHECK=SEMANTICS iname=CDBInteractor.pc parse=none code=cpp cpp_suffix=cpp
g++ -c main.cpp
g++ -o pre_request_engine main.o -I/oracle/oracle/app/product/10g/precomp -L/oracle/oracle/app/product/10g/lib32 -lnsl -ldl
And... (2 Replies)
Discussion started by: tushar_tus
2 Replies
8. Programming
Hello,
My problem is with compiling a program modelling shallow water.
In it there is a subroutine called stat with 9 parameters.
In the main program it is called with 9 parameters also
I'm running Ubuntu 11.04 with gfortran version 4.5.
Thanks.
---------- Post updated at 11:57 PM... (0 Replies)
Discussion started by: b_franz
0 Replies
9. Programming
Hello,
I hope this is the correct forum for this post. I have the following
problem:
A Fortran 77 program that has to deal with several large
matrices (each approx. 5000 x 5000) and uses lapack and blas
subroutines has been correctly compiled and executed using Debian
Etch. When I tried... (1 Reply)
Discussion started by: currix
1 Replies
10. Programming
I've received some executable script for test, but executing this script continuously give me following message
./example: error while loading shared libraries: libgfortran.so.1: cannot open shared object file: No such file or directory
Google search told me to do as following
$... (1 Reply)
Discussion started by: exsonic
1 Replies
LEARN ABOUT OSF1
releaseobj
atom_object_management(5) File Formats Manual atom_object_management(5)
NAME
atom_object_management, BuildObj, IsObjBuilt, WriteObj, ReleaseObj - Allows an Atom tool's InstrumentAll routine to build, release, and
write objects
SYNOPSIS
#include <cmplrs/atom.inst.h>
unsigned BuildObj(
Obj * ); unsigned IsObjBuilt(
Obj * ); void WriteObj(
Obj * ); void ReleaseObj(
Obj * );
DESCRIPTION
Atom's object management routines allow an Atom tool's InstrumentAll routine to build, write, and release objects.
You can use these routines only from an Atom tool's instrumentation file. See atom(1) for a description of Atom.
An InstrumentAll routine must call the BuildObj routine before calling AddCallObj to add analysis routine calls to the object and before
traversing the procedures in the object. BuildObj builds the internal data structures Atom uses to manipulate the object. After the Atom
tool traverses and instruments the object, the InstrumentAll routine must call the WriteObj routine to write out the instrumented version
of the object. For example:
unsigned InstrumentAll(int iargc, char **iargv) {
Obj * obj;
AddCallProto("Startup()");
AddCallProto("Finish()");
AddCallProto("foo(int, REGV)");
AddCallProgram(ProgramBefore, "Startup");
AddCallProgram(ProgramAfter, "Finish");
for (obj = GetFirstObj(); obj; obj = GetNextObj(obj))
{
if (BuildObj(obj))
return(1);
/* instrument obj */
WriteObj(obj);
}
return(0); }
The WriteObj routine writes the instrumented version of the specified object, deallocating the internal data structures BuildObj previously
created.
Note that BuildObj may return an error code. It returns a nonzero value (and issues an appropriate error message) if it encounters an error
in the executable file for the Obj0. You should propagate this error value back to Atom by returning 1 from InstrumentAll.
The ReleaseObj routine deallocates the internal data structures for the given object, but does not write out the instrumented version the
object. You should not call ReleaseObj if you have added any analysis routine calls to the object.
The IsObjBuilt routine returns a nonzero value if the specified object has been built with BuildObj, but not yet written with WriteObj or
unbuilt with ReleaseObj.
Whenever possible, tools should build and write out each object only once. Some tools, however, may build and release an object several
times, ultimately writing out its instrumented version. This can be very time-consuming for a tool with very large objects.
Similarly, tools should normally build only one object at a time. Certain tools may simultaneously build several objects, instrument each
one, and then write each out. This has advantages for tools that call ResolveNamedProc or ResolveTargetProc. However, having more than one
large object built at a single time will cause Atom to run slowly and to consume a large amount of memory.
RETURN VALUES
These routines return values as described above.
FILES
Header file containing external definitions of Atom routines
SEE ALSO
Commands: atom(1)
AtomTools: hiprof(5), pixie(5), third(5)
Functions: atom_application_instrumentation(5), atom_application_query(5), atom_application_navigation(5), atom_description_file(5),
atom_application_resolvers(5), atom_instrumentation_routines(5), AnalHeapBase(5), Xlate(5), Thread(5)
Programmer's Guide
atom_object_management(5)