08-11-2009
-bloadmap function in aix
hi everyone!!i hope that all the members are in great mood!!
i'm porting a product from AIX system compiled with xlc to RHEL5 with GCC as compiler:
now i'm stuck with this option that i didn't find in gcc manual:
-bloadmap:eds.map
i hope that u help me figure this out and thanks to all the work that u do here!!
10 More Discussions You Might Find Interesting
1. AIX
I am having a strange problem with the poll() routine. I compiled a module under AIX 5.2 using the poll routine, it worked fine. When the OS was upgraded to AIX 5.3 the poll routine return an error code.
Here is a summary of the code:
#define MAX_EVENTS 300
long eventCount;... (0 Replies)
Discussion started by: TahirNazir
0 Replies
2. Shell Programming and Scripting
Hi ,
I have three funcions f1, f2 and f3 .
f1 calls f2 and f2 calls f3 .
I have a global variable "period" which i want to pass to f3 .
Can i pass the variable directly in the definition of f3 ?
Pls help .
sars (4 Replies)
Discussion started by: sars
4 Replies
3. Shell Programming and Scripting
I have two scripts. script1.sh looks
--------------------------------
#!/bin/bash
display()
{
echo "Welcome to Unix"
}
display
-----------------------------
Script2.sh
#!/bin/bash
sh script1.sh //simply calling script1.sh
------------------------------ (1 Reply)
Discussion started by: mvictorvijayan
1 Replies
4. Shell Programming and Scripting
This is my function which is creating three variables based on counter & writing these variable to database by calling another function writeRecord
but only one record is getting wrote in DB.... Please advise ASAP...:confused:
function InsertFtg
{
FTGSTR=""
echo "Saurabh is GREAT $#"
let... (2 Replies)
Discussion started by: omkar.sonawane
2 Replies
5. Programming
In gdb, I can call one function with command "call", but how can I step in the function? I don't want to restart the program, but the function had been executed, gdb will execute next statement, and I don't know how to recall the function. (4 Replies)
Discussion started by: 915086731
4 Replies
6. Shell Programming and Scripting
I have a script which does gunzip, zip and untar.
Input to the script is file name and file directory (where file is located)
I am reading the input parameters as follows:
FILENAME=$1
FILEDIR=$2
I have created 3 functions that are as follows:
1) gunzip file
2) unzip file... (2 Replies)
Discussion started by: pinnacle
2 Replies
7. UNIX Desktop Questions & Answers
dear friends
I have a wrote a shell script which works like this.
1.) a command is executed and the log is moved in the file.
2.) this file is copied in to the other file.
3.) used a grep command to find a particular word.
4.) if a particular word is there then the script will go to next... (4 Replies)
Discussion started by: aboy212u
4 Replies
8. Shell Programming and Scripting
Hello,
I am reading one of the AIX manuals about shell scripting and (AIX 5) and I found this example when introducing to functions:
function usage
{
prog="$1"; shift
print -u2 "$prog: usage: $prog $@"
exit 1
}
This example is meant to be easy but I don't understand what it is... (5 Replies)
Discussion started by: Kibou
5 Replies
9. Shell Programming and Scripting
Dear All.
I have a script, which process files one by one. In the script I have two functions.
one sftp files to different server
the other from existing file create file with different name.
My question is:
Will sftp function recognize files names , which are created in another... (1 Reply)
Discussion started by: digioleg54
1 Replies
10. Shell Programming and Scripting
Hi All,
Good Day, seeking for your assistance on how to not perform my 2nd, 3rd,4th etc.. function if my 1st function is in else condition.
#Body
function1()
{
if
then
echo "exist"
else
echo "not exist"
}
#if not exist in function1 my all other function will not proceed.... (4 Replies)
Discussion started by: meister29
4 Replies
LEARN ABOUT CENTOS
error::sdt
ERROR::SDT(7stap) ERROR::SDT(7stap)
NAME
error::sdt - <sys/sdt.h> marker failures
DESCRIPTION
Systemtap's <sys/sdt.h> probes are modeled after the dtrace USDT API, but are implemented differently. They leave a only a NOP instruction
in the userspace program's text segment, and add an ELF note to the binary with metadata. This metadata describes the marker's name and
parameters. This encoding is designed to be parseable by multiple tools (not just systemtap: GDB, the GNU Debugger, also contains sup-
port). These allow the tools to find parameters and their types, wherever they happen to reside, even without DWARF debuginfo.
The reason finding parameters is tricky is because the STAP_PROBE / DTRACE_PROBE markers store an assembly language expression for each op-
erand, as a result of use of gcc inline-assembly directives. The compiler is given a broad gcc operand constraint string ("nor") for the
operands, which usually works well. Usually, it does not force the compiler to load the parameters into or out of registers, which would
slow down an instrumented program. However, some instrumentation sites with some parameters do not work well with the default "nor" con-
straint.
unresolveable at run-time
GCC may emit strings that an assembler could resolve (from the context of compiling the original program), but a run-time tool can-
not. For example, the operand string might refer to a label of a local symbol that is not emitted into the ELF object file at all,
which leaves no trace for the run-time. Reference to such parameters from within systemtap can result in "SDT asm not understood"
errors.
too complicated expression
GCC might synthesize very complicated assembly addressing modes from complex C data types / pointer expressions. systemtap or gdb
may not be able to parse some valid but complicated expressions. Reference to such parameters from within systemtap can result in
"SDT asm not understood" errors.
overly restrictive constraint
GCC might not be able to even compile the original program with the default "nor" constraint due to shortage of registers or other
reasons. A compile-time gcc error such as "asm operand has impossible constraints" may result.
There are two general workarounds to this family of problems.
change the constraints
While compiling the original instrumented program, set the STAP_SDT_ARG_CONSTRAINT macro to different constraint strings. See the
GCC manual about various options. For example, on many machine architectures, "r" forces operands into registers, and "g" leaves
operands essentially unconstrained.
revert to debuginfo
As long as the instrumented program compiles, it may be fine simply to keep using <sys/sdt.h> but eschew extraction of a few indi-
vidual parameters. In the worst case, disable <sys/sdt.h> macros entirely to eschew the compiled-in instrumentation. If DWARF
debuginfo was generated and preserved, a systemtap script could refer to the underlying source context variables instead of the
positional STAP_PROBE parameters.
SEE ALSO
stap(1),
stapprobes(3stap),
error::dwarf(7stap),
http://gcc.gnu.org/onlinedocs/gcc/Constraints.html,
http://sourceware.org/systemtap/wiki/UserSpaceProbeImplementation,
error::reporting(7stap)
ERROR::SDT(7stap)