10 More Discussions You Might Find Interesting
1. How to Post in the The UNIX and Linux Forums
Hi All,
Please help me and guide me to write a bash/shell script on Linux box to delete parent entry with all their child entries.
example:
Parent is :
----------
dn: email=yogesh.kumar@wipro.com, o=wipro, o=in
child is:
----------
dn: cn: yogesh kumar, email=yogesh.kumar@wipro.com,... (1 Reply)
Discussion started by: Chand
1 Replies
2. Programming
Hello to all
I want download a file in osx intel 64 with NASM , I want to use socket syscall
This is part of my code
section .data
command db "GET /test/2.gif HTTP/1.1\r\nHost: 10.1.1.187\r\n\r\n", 0
; url db "http://172.16.207.153/test/2.gif", 0
global main... (1 Reply)
Discussion started by: recher.jack
1 Replies
3. UNIX for Advanced & Expert Users
Hello Experts,
If a Solaris process is calling some syscall, and right now execution is inside syscall doing only CPU work, for example the inside simplest times syscall,
-> app_func
=> times
<< we are here now, we have entered in the times, but not exited yet
<= times
<- app_func... (9 Replies)
Discussion started by: sant
9 Replies
4. SCO
Hello,
is there any command in SCO unix by which I can check if the file system is HTFS or DTFS?
Thanks (1 Reply)
Discussion started by: Mick
1 Replies
5. UNIX for Dummies Questions & Answers
I saw somewhere that describe read() as a primitive. But when I lean signals, it says the read() may be interrupted by a signal.
My Question:
1, What is the diffence between primitive and reentrant?
2, Is read() a primitive or reentrant?
3, Are all system calls primitive or reentrant? (2 Replies)
Discussion started by: vistastar
2 Replies
6. Programming
Hi all,
i just started started learning system programming and want to pursue a career in the sys prog area.
below is the program that use a fork() call.
i read in one of the tutorials that parent process and child process uses different address spaces and runs concurrently.
that meas each... (2 Replies)
Discussion started by: MrUser
2 Replies
7. Programming
I am working on solaris 9. and use gmake to compile and linke c/c++ program.
anybody can tell me the distinguish between gmake and make? :confused: (10 Replies)
Discussion started by: robin.zhu
10 Replies
8. HP-UX
how to distinguish different files and choose a mode while ftp?means which modes ascii or binary for zip(.gz) ,.txt,.sh,.dat and executable as well as movie files. (1 Reply)
Discussion started by: megh
1 Replies
9. Programming
I have a question regarding the recv syscall.
Suppose I have a client/server and the following exchange of message took place:
Client --> Server using multiple send syscalls one after another immediately:
send "Packet1"
send "Packet2"
send "Packet3"
Server receives in the... (2 Replies)
Discussion started by: heljy
2 Replies
10. AIX
Hello,
In a script shell, I have a variable containing the name of a file and I would like to distinguish the name from the extention of the file. For example, the file 'myfile.txt' is in a variable called $VAR. How can I obtain 2 variables, one with 'myfile' and the other with 'txt' ?
Thank you (2 Replies)
Discussion started by: tbeghain
2 Replies
PTRACE(2) BSD System Calls Manual PTRACE(2)
NAME
ptrace -- process tracing and debugging
SYNOPSIS
#include <sys/types.h>
#include <sys/ptrace.h>
int
ptrace(int request, pid_t pid, caddr_t addr, int data);
DESCRIPTION
ptrace() provides tracing and debugging facilities. It allows one process (the tracing process) to control another (the traced process).
Most of the time, the traced process runs normally, but when it receives a signal (see sigaction(2)), it stops. The tracing process is
expected to notice this via wait(2) or the delivery of a SIGCHLD signal, examine the state of the stopped process, and cause it to terminate
or continue as appropriate. ptrace() is the mechanism by which all this happens.
The request argument specifies what operation is being performed; the meaning of the rest of the arguments depends on the operation, but
except for one special case noted below, all ptrace() calls are made by the tracing process, and the pid argument specifies the process ID of
the traced process. request can be:
PT_TRACE_ME This request is one of two used by the traced process; it declares that the process expects to be traced by its parent. All
the other arguments are ignored. (If the parent process does not expect to trace the child, it will probably be rather con-
fused by the results; once the traced process stops, it cannot be made to continue except via ptrace().) When a process has
used this request and calls execve(2) or any of the routines built on it (such as execv(3)), it will stop before executing the
first instruction of the new image. Also, any setuid or setgid bits on the executable being executed will be ignored.
PT_DENY_ATTACH
This request is the other operation used by the traced process; it allows a process that is not currently being traced to deny
future traces by its parent. All other arguments are ignored. If the process is currently being traced, it will exit with the
exit status of ENOTSUP; otherwise, it sets a flag that denies future traces. An attempt by the parent to trace a process which
has set this flag will result in a segmentation violation in the parent.
PT_CONTINUE The traced process continues execution. addr is an address specifying the place where execution is to be resumed (a new value
for the program counter), or (caddr_t)1 to indicate that execution is to pick up where it left off. data provides a signal
number to be delivered to the traced process as it resumes execution, or 0 if no signal is to be sent.
PT_STEP The traced process continues execution for a single step. The parameters are identical to those passed to PT_CONTINUE.
PT_KILL The traced process terminates, as if PT_CONTINUE had been used with SIGKILL given as the signal to be delivered.
PT_ATTACH This call has been replaced with PT_ATTACHEXC.
PT_ATTACHEXC This request allows a process to gain control of an otherwise unrelated process and begin tracing it. It does not need any
cooperation from the to-be-traced process. In this case, pid specifies the process ID of the to-be-traced process, and the
other two arguments are ignored. This request requires that the target process must have the same real UID as the tracing
process, and that it must not be executing a setuid or setgid executable. (If the tracing process is running as root, these
restrictions do not apply.) The tracing process will see the newly-traced process stop and may then control it as if it had
been traced all along. Note that this call differs from the prior call ( PT_ATTACH) in that signals from the child are deliv-
ered to the parent as Mach exceptions (see EXC_SOFT_SIGNAL).
PT_DETACH This request is like PT_CONTINUE, except that it does not allow specifying an alternate place to continue execution, and after
it succeeds, the traced process is no longer traced and continues execution normally.
ERRORS
Some requests can cause ptrace() to return -1 as a non-error value; to disambiguate, errno can be set to 0 before the call and checked after-
wards. The possible errors are:
[ESRCH]
No process having the specified process ID exists.
[EINVAL]
o A process attempted to use PT_ATTACHEXC on itself.
o The request was not one of the legal requests.
o The signal number (in data) to PT_CONTINUE was neither 0 nor a legal signal number.
o PT_GETREGS, PT_SETREGS, PT_GETFPREGS, or PT_SETFPREGS was attempted on a process with no valid register set. (This is normally
true only of system processes.)
[EBUSY]
o PT_ATTACHEXC was attempted on a process that was already being traced.
o A request attempted to manipulate a process that was being traced by some process other than the one making the request.
o A request (other than PT_ATTACHEXC) specified a process that wasn't stopped.
[EPERM]
o A request (other than PT_ATTACHEXC) attempted to manipulate a process that wasn't being traced at all.
o An attempt was made to use PT_ATTACHEXC on a process in violation of the requirements listed under PT_ATTACHEXC above.
BSD
March 25, 2015 BSD