12-20-2008
Hey, Jim, thanks for the tip, it is really encouraging! You are right, it is not a problem of size of the storage. It is my program error. My unfinished makefile didn't automatically delete the old library I generated before linking, and leads to prototype mismatch from signed type to unsigned type. And I am totally lost while playing with long int, long long int and other datatypes while the old library file is there! Thanks!
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Whats the difference between 32bit and 64bit OS's or applications. I understand it a little but its just not clicking the way the teacher explained to me
thanks, any info would be much appreciated (1 Reply)
Discussion started by: eloquent99
1 Replies
2. Shell Programming and Scripting
Can one string type variable changed into the date type variable. (1 Reply)
Discussion started by: rinku
1 Replies
3. Programming
Dear colleagues,
One of my friend have a problem with c code. While compiling a c program it displays a message like
"array type has incomplete element type". Any body can provide a solution for it.
Jaganadh.G (1 Reply)
Discussion started by: jaganadh
1 Replies
4. Solaris
AIM- Install Oracle 11g on Solaris using VMWare
Steps
1.Logged on as root
2.Created subfolders à /usr/local/bin & /usr/local/bin/gcc
3.Downloaded gcc & libiconv & unzipped them on my harddrive & burnt them on CD
4.Copied files from CD to /usr/local/bin/gcc
5.Terminal (root) à pkgadd -d... (8 Replies)
Discussion started by: Ackers
8 Replies
5. Programming
Hi all, this warning is driving me nuts. I use -pedantic with -Wall and -Werror so this needs to be fixed.
BUILD: GNU-Linux-x86
Any ideas?
struct sockaddr_in server_addr;
int addr_len = sizeof (server_addr);
fd = accept(link->socket_fd,
(struct sockaddr_in *)... (2 Replies)
Discussion started by: personificator
2 Replies
6. Programming
Currently my Pro*c program is fetching a cloumn which is defined as LONG in oracle db. The data in the column is around 65k. But when I am FETCHing it to a varchar variable, I am only getting 22751 bytes of data using cursor.
Is there any limitation on the data which is fetched by a cursor in... (2 Replies)
Discussion started by: manbt
2 Replies
7. Red Hat
Hi Friends,
Please help me to understand, how to enable async disk IO and Direct disk IO in ext3 filesystem on rhel5.
Regards,
Arumon (0 Replies)
Discussion started by: arumon
0 Replies
8. Shell Programming and Scripting
Hi,
I want to extract a XML file which is stored in the database having a data Type as "LONG" via UNIX Scripting.
But when i am triggering the SQL via UNIX it is fetching only the first Line and not the complete XML.
Can you please suggest if the parameters that i have used needs any... (0 Replies)
Discussion started by: dear_abhi2007
0 Replies
9. Shell Programming and Scripting
Hi,
I want to extract a XML file which is stored in the database having a data Type as "LONG" via UNIX Scripting.
But when i am triggering the SQL via UNIX it is fetching only the first Line and not the complete XML.
Can you please suggest if the parameters that i have used needs any... (2 Replies)
Discussion started by: Barbara1234
2 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)