03-15-2011
The linux debugger is based on the ptrace system call. Every different unix OS has its own version of ptrace - it may be called something else.
Consider looking at ptrace. Using the api for gdb will be more trouble than benefit.
Look into gprof and gcover as well. Consider that with all of the effort put into gcover, gprof, and gdb -- the people who have developed them over the past 15 years have got a handle on uses and presented them to us.
In other words, corona's assessment is correct - it ain't worth the time and frustration.
9 More Discussions You Might Find Interesting
1. Programming
Can any one help me out????
I need to install GDB and GCC in an UNIX machine.
can any one point me to any lucid pointer to it.
The gNU help on this is proving to be little tangential for me. (2 Replies)
Discussion started by: rraajjiibb
2 Replies
2. Shell Programming and Scripting
Is there a command in unix to find the union of two files and removing the union from one of the files?
e.g. I have two files input1.txt and input2.txt with the contents below:
$ more input1.txt
4
2
3
2
$ more input2.txt
5
4
4
8
2
I want to find the union of the two and... (7 Replies)
Discussion started by: stevefox
7 Replies
3. Shell Programming and Scripting
Given two files of the same format (For example number1|text1|number2) what is the command to print lines in file1 which do not occur in file2? diff command seems a bit complicated for me for this purpose. Please help!! Thank you very much. (3 Replies)
Discussion started by: sherkaner
3 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. UNIX for Advanced & Expert Users
Hi,
This is a simple question on GDB. Given a core file, how can you check which process has dumped the core?
Regards
- Krishna (1 Reply)
Discussion started by: krishnamurthig
1 Replies
6. Shell Programming and Scripting
How can i union two files that each of them contain text to one new file in unix shell scripting or in awk scripting language? (2 Replies)
Discussion started by: tal
2 Replies
7. Shell Programming and Scripting
Hi all,
I have difficulty to solve the followign problem.
mydata:
StartPoint EndPoint
22 55
2222 2230
33 66
44 58
222 240
11 25
22 60
33 45
The union of above... (2 Replies)
Discussion started by: phoeberunner
2 Replies
8. Web Development
Hi,
A piece of script from Perl-cookbook I do not understand, and post here for explanation.
The purpose is to find the element in either array (union), and in both array (intersection). Thank you in advance.
@a=qw(1 3 5 6 7 8);
@b=qw(2 3 5 7 9);
foreach $e (@a, @b) {$union{$e}++ &&... (3 Replies)
Discussion started by: yifangt
3 Replies
9. Programming
Sorry for the “word salad” subject, but I wanted to cast a wide net for help.
I've created an IP (Internet Protocol) server which serves HTTP, SMTP, and FTP requests.
As you probably know, they all require creating a socket, listening on it, accepting connections, and then having a short... (3 Replies)
Discussion started by: John S.
3 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)