Do...
ls -l /usr/lib/syscalls.imp
lslpp -l bos.adt.syscalls
when I try the first command I got this message :
the second one displays this result:
any idea ?
---------- Post updated at 03:45 AM ---------- Previous update was at 03:37 AM ----------
Thank you bakunin
Quote:
You don't. SUMA will just help you download all the necessary dependencies
I didn't mention that I'm so new to this environement, I begin working on AIX last week
Quote:
Have you considered updating to 6.1 or 7.1 ?
Could you give me a link or something to help me to improve my level on it, and discovering how to update to 6.1 or 7.1 ? (the company I'm working for, use AIX 5.3 for years ago, updating to 6.1 or 7.1 will be a simple operation ? )
Hi ,
attempting to purify code on the link line generates a fatal error
like this
#ERROR: (fatal) Cannot find libtest.so in the search path .
command line:
-------------
purify -show-directory=yes -always-use-cache-dir -cache-dir=/ppic/users/avadhani/sgi/pure /usr/bin/CC -n32 -mips3... (2 Replies)
Hi,
I am facing problem while doing build on AIX using xlC compiler. We are using purify. Purify fails to instrument the a few libraries. Interestingly these are not developed by us and are 3rd party SW components. Can someone let me know how to proceed with the build?
Here is the output... (0 Replies)
Hi,
I am using purify to find memory leak in my process.
When I run the instrumented program I get error
I donot have this file in the specified directory. Instead I have following files in the directory /usr/lib/nls/loc/locales.2
What should I do in such case? I undersatnd... (1 Reply)
Hi, my IBM 9117-570 model (mounting SF230_126 firmware version) gives an errpt like the following. The problem is that no SRC code found at IBM information center web site. Some ideas where are those SRC searchable ?
O.S. is AIX 5.2-
tkx
E18E984F 1119200506 P S SRC ... (0 Replies)
Hi, i'm trying to work with a trial version of PurifyPlus 7 with fixpack 10 from Rational that needs to run over an AIX 5.3 platform, 64-bit. I had success on compiling and running the hello_world programs and even a hash test program i found over the net, but purify can achieve the same with the... (0 Replies)
#!/bin/csh
#
# Time of day greeting
#
# usage: greet
#
if ($#argv == 0) then
set hour = ‘date +%H’
else
set hour = $argv
endif
#
if ($hour < 12) then
echo "Good Morning\!"
else
if ($hour < 18) then
echo "Good Afternoon\!"
... (2 Replies)
Hi
Rational® Purify® is a dynamic software analysis tool - helps to clean your own C or C++ code from memory leak problems etc.
Who knows some compatable (my be freeware) software? (1 Reply)
Hi
I am facing a problem while doing Purify Instrumentation of the Informix ESQL-C files. The system is RedHat Linux 5.6 and compiler is gcc.
I have set both CC and INFORMIXC variables to "purify gcc" and compiled the source code. All the .c and .ec files were compiled successfully,
but... (0 Replies)
I just installed IBM PurifyPlus on IBM AIX 5.3 and they suggested me to run the command through the following one:
% purify cc -g hello_world.c
but it's giving me the message that :
purify command not found
I need your help
Thanks In Advance (10 Replies)
when i instrument ourify i am getting error like
.*** OI_init: Error, cannot connect to X server
Purify or PureCoverage slave: Warning: Can't open display "localhost:0", using tty mode.
. Got it]
I am using AIX1.6 OS
i have xwin32 installed in my windows.. (1 Reply)
Discussion started by: greenworld123
1 Replies
LEARN ABOUT NETBSD
compat_30
COMPAT_30(8) BSD System Manager's Manual COMPAT_30(8)NAME
compat_30 -- setup procedure for backward compatibility on post-3.0 releases
SYNOPSIS
options COMPAT_30
DESCRIPTION
The compat_30 module allows NetBSD to run NetBSD 3.0 executables.
The support is present if the kernel was built with option COMPAT_30. It is not available as a loadable module.
Static executables typically need no additional setup. Dynamic binaries may require shared libraries whose major version number changed
since NetBSD 3.0, which are listed below. A shadow directory under /emul is not used; the libraries can be obtained from a NetBSD 3.0 dis-
tribution and installed in the original directories shown, as the major version number in the file name will prevent conflicts. If an
upgrade installation from NetBSD 3.0 has been done and these libraries are still present, nothing more need be done.
Libraries needed from 3.0
/lib/libcrypto.so.2.1 /lib/libcrypto.so.2
/usr/lib/libcrypto.so.2.1 /usr/lib/libcrypto.so.2
/lib/libevent.so.0.2 /lib/libevent.so.0
/usr/lib/libevent.so.0.2 /usr/lib/libevent.so.0
/usr/lib/libg2c.so.2.0 /usr/lib/libg2c.so.2
/usr/lib/libkadm.so.5.0 /usr/lib/libkadm.so.5
/usr/lib/libkafs.so.6.0 /usr/lib/libkafs.so.6
/usr/lib/libkdb.so.5.0 /usr/lib/libkdb.so.5
/usr/lib/libkrb5.so.19.1 /usr/lib/libkrb5.so.19
/usr/lib/libkrb.so.6.0 /usr/lib/libkrb.so.6
/usr/lib/libkstream.so.2.0 /usr/lib/libkstream.so.2
/usr/lib/libmagic.so.0.1 /usr/lib/libmagic.so.0
/usr/lib/libpcap.so.1.4 /usr/lib/libpcap.so.1
/lib/libradius.so.0.0 /lib/libradius.so.0
/usr/lib/libradius.so.0.0 /usr/lib/libradius.so.0
/usr/lib/libssh.so.1.0 /usr/lib/libssh.so.1
/usr/lib/libssl.so.3.0 /usr/lib/libssl.so.3
/usr/lib/libstdc++.so.5.0 /usr/lib/libstdc++.so.5
/lib/libz.so.0.4 /lib/libz.so.0
/usr/lib/libz.so.0.4 /usr/lib/libz.so.0
/usr/lib/libamu.so.2.1 /usr/lib/libamu.so.2
IMPLEMENTATION NOTES
COMPAT_30 enables the NetBSD 3.0 versions of the following system calls, whose syscall numbers and argument structures were changed after the
3.0 release to accommodate 64-bit filesystems: fhstat(2), fstat(2), getdents(2), lstat(2), stat(2).
The filehandle structure (formerly fhandle_t) was made opaque to userland and variable-sized. A fh_size argument was added to related
syscalls: fhstat(2), fhstatvfs(2), fhstatvfs1(2), fhopen(2), getfh(2). This changes the API and ABI of those syscalls, COMPAT_30 enables
binary compatibility with the old ABI. Source compatibility is not provided, as use of those syscalls is supposed to be rare.
The error code from the socket(2) syscall changed from EPROTONOSUPPORT to EAFNOSUPPORT in the case of an unsupported address family.
COMPAT_30 enables binary compatibility with the old ABI. Source compatiblility is not provided.
The struct ntptimeval used by ntp_gettime(2) changed with the implementation of timecounters.
SEE ALSO config(1), fhstat(2), fstat(2), getdents(2), lstat(2), stat(2), options(4)HISTORY
NetBSD offers back-compatibility options back to NetBSD 0.9, but the first to be documented with a manual page is compat_30.
BUGS
The compatible getdents(2) is unable to see directory entries beneath the top layer of a union, even though the real 3.0 getdents() did not
have that problem.
SECURITY CONSIDERATIONS
Programs with security impact that receive incorrect directory contents from getdents() may behave improperly, as when they are unable to
find, or find the wrong versions of, important files.
BSD December 15, 2007 BSD