08-05-2009
Thanks for all your support guys.
I am now able to resolve the error-
I have just set OBJECT_MODE variable-
export OBJECT_MODE=64(for ksh)
9 More Discussions You Might Find Interesting
1. Programming
Hello,
when i compile with xlc on aix i got the error message "ld: 0711-317 ERROR: Undefined symbol: .hello"
dummy.pc:
#include <stdio.h>
#include <stdlib.h>
#include <string.h>
#include "dummy.h"
int main ( )
{
printf("\nbefore Hello");
hello();
printf("\npast Hello"); ... (2 Replies)
Discussion started by: stockdan
2 Replies
2. UNIX for Dummies Questions & Answers
Hey guys, need some help. Running AIX Version 5.2 and one of our cron jobs is writing errors to a log file. Any ideas on the following error message.
Error: Internal system error: Unable to initialize standard output file
I'm guessing more info might be needed, so let me know.
Thanks (2 Replies)
Discussion started by: firkus
2 Replies
3. UNIX for Dummies Questions & Answers
hi there
i write one awk script file in shell programing
the code is related to dd/mm/yy to month, day year format
but i get an error
please can anybody help me out in this problem ??????
i give my code here including error
awk `
# date-month -- convert mm/dd/yy to month day,... (2 Replies)
Discussion started by: Herry
2 Replies
4. AIX
--------------------------------------------------------------------------------
Hello, help me please.
I am trying to create a mksysb bakup using nim. I am geting this error, how to correct it ? :
Command : failed stdout: yes stderr: no... (9 Replies)
Discussion started by: astjen
9 Replies
5. Programming
I am trying to compile pro*c program on aix 5.3. The program compiled fine when I was using curses library. After switching to ncurses, I have started getting compilation errors. After installing ncurses on the box, I changed the -lcurses flag to -lncurses. I have also updated the path to the... (13 Replies)
Discussion started by: wvuguy
13 Replies
6. UNIX for Dummies Questions & Answers
im kinda new to shell scripting so i need some help
i try to run this script and get the error code
> 5 ")syntax error: operand expected (error token is "
the code for the script is
#!/bin/sh
#
# script to see if the given value is correct
#
# Define errors
ER_AF=86 # Var is... (4 Replies)
Discussion started by: metal005
4 Replies
7. AIX
I need to install python 3.3.0 to AIX 6.1
I created folder where I want to install
I downloaded files archive from python official website
I extracted it into new folder and ran;
1)./configure --with-gcc="xlc_r" --with-cxx="xlC_r" --disable-ipv6 --prefix=my_folder CXX=xlC_r... (2 Replies)
Discussion started by: AIX_30
2 Replies
8. Solaris
I have two servers with a fresh install of Solaris 11, and having problems when doing rpcinfo between them. There is no firewall involved, so everything should theoretically be getting through. Does anyone have any ideas? I did a lot of Google searches, and haven't found a working solution yet.
... (2 Replies)
Discussion started by: christr
2 Replies
9. UNIX for Beginners Questions & Answers
I am writing a shell script with 2 run time arguments. During the execution if i got any error, then it needs to redirected to a error file and in console. Also both error and output to be redirected to a log file. But i am facing the below error.
#! /bin/sh
errExit ()
{
errMsg=`cat... (1 Reply)
Discussion started by: sarathy_a35
1 Replies
LEARN ABOUT CENTOS
error::buildid
ERROR::BUILDID(7stap) ERROR::BUILDID(7stap)
NAME
error::buildid - build-id verification failures
DESCRIPTION
Because systemtap's script translation / execution stages may be executed at different times and places, it is sometimes necessary to ver-
ify certain invariants. One such invariant is that if a script was informed by translate-time analysis of executables, then those same
executables need to be used at run time. This checking is done based upon the build-id, a binary hash that modern (post-2007) compil-
ers/toolchains add as an NT_GNU_BUILD_ID ELF note to object files and executables. Use the readelf -n command to examine the build-ids of
binaries, if you are interested.
Only scripts are sensitive to executables' build-ids: generally those that perform deep analysis of the binaries or their debuginfo. For
example, scripts that place .function or .statement probes, or use stack backtrace-related tapset functions may be sensitive. Other
scripts that rely only on process.mark or kernel.trace probes do not require debuginfo. See the DWARF DEBUGINFO section in the stap-
probes(3stap) man page.
During translation, systemtap saves a copy of the relevant files' build-ids within the compiled modules. At run-time, the modules compare
the saved ones to the actual run-time build-ids in memory. The error message indicates that they did not match, so the module will decline
placing a probe that was computed based upon obsolete data. This is important for safety, as placing them at an inappropriate address
could crash the programs. However, this is not necessarily a fatal error, since probes unrelated to the mismatching binaries may operate.
A build-id mismatch could be caused by a few different situations. The main one is where the executable versions or architecture were dif-
ferent between the systemtap translation and execution times/places. For example, one may run a stap-server on a slightly different ver-
sion of the OS distribution. The kernel running on the workstation may be slightly different from the version being targeted - perhaps due
to a pending kernel upgrade leaving different files on disk versus running in memory. If your OS distribution uses separate debuginfo
packages, the split .IR .debug files may not exactly match the main binaries.
SEE ALSO
http://fedoraproject.org/wiki/Releases/FeatureBuildId,
stap(1),
stapprobes(3stap),
warning::debuginfo(7stap),
error::reporting(7stap)
ERROR::BUILDID(7stap)