02-11-2005
Quote:
Originally Posted by jim mcnamara
OP wants to know if a function can do a stack crawl to find the address of the calling function - I do not know how.
Does the OP mean the address of the CPU stack pointers? If so, I don't think this is available at the OS level. That is why, as I recall (it has been many years), there are "buffer overflows" and similar security issues, because the OS and application does not have direct visibility into the addresses of the CPU H/W stack.
10 More Discussions You Might Find Interesting
1. Cybersecurity
they are having an operator call my home line and also my cell number and they are typing and the operator tells me what they are typing on their computer. i nevere heard of this. it is new to me. it is free the operator said, they knew my name and also a friend of mine's name...the phone says the... (2 Replies)
Discussion started by: gail
2 Replies
2. UNIX for Dummies Questions & Answers
Hello.
I want to copy temp files when I make a new file by vi.
For example,
09:32:52 ~/ $ mkdir test
09:33:03 ~/ $ cd test/
09:33:09 ~/test/ $ ls
09:33:16 ~/test/ $ vi test.cpp
09:34:37 ~/test/ $ cat test.cpp
#include <iostream>
int main()
{
}
09:34:48 ~/test/ $ vi test.bash
09:35:19... (1 Reply)
Discussion started by: Euler04
1 Replies
3. UNIX for Dummies Questions & Answers
I have created a shortcut for the file kill_process.sh as shown below.
alias kill_process="sh /root/kill_process.sh"
It is working as per my expectations. But I have 2 questions.
1) Is there any better way?
2) How do I check what does kill_process link to? (1 Reply)
Discussion started by: shantanuo
1 Replies
4. Programming
Hi,
I am trying to execute a perl script from c program.
I tried using system command.
system("perl test.pl filename") ;
This perl program takes filename as input and prints a number
to screen.
I need to get that returned number in C program.
system command is... (3 Replies)
Discussion started by: pkusumam
3 Replies
5. Shell Programming and Scripting
Hi,
How to call a file in shell script?
I need to execute a file in shell script whether its possibel if it please give some example
please help me (4 Replies)
Discussion started by: thelakbe
4 Replies
6. Homework & Coursework Questions
Use and complete the template provided. The entire template must be completed. If you don't, your post may be deleted!
1. The problem statement, all variables and given/known data:
I must write a shell script that calls two external Perl functions--one of which sorts the data in a file, and... (6 Replies)
Discussion started by: kowit010
6 Replies
7. Shell Programming and Scripting
Hi. I have been running some scripts ok with no extension on the name, and they work fine. What difference does it make if I call them whatever.sh? And I have some scripts starting #!/bin/bash - which debian recognises as shell scritps, even without the .sh ending - and some which don't. I'm sure... (8 Replies)
Discussion started by: triplemaya
8 Replies
8. Shell Programming and Scripting
Greetings all,
I am calling a remove from within a script that is used for a cleanup process.. It is not working as expected. Here is what I am doing.
I have a config file that lists out a directory name, and the options to run
Within the config file
DIR1="find... (9 Replies)
Discussion started by: jeffs42885
9 Replies
9. Shell Programming and Scripting
Hello
Current working script is :
#
# my_script BEGIN
#
function a_function {
FIRST_PARAM="$1"
DO_SOMETHING "$FIRST_PARAM"
}
export -f a_function
START_HERE="/home/some_user/Documents"
find $START_HERE" -exec bash -c 'a_function "$0" ' {} \; (5 Replies)
Discussion started by: jcdole
5 Replies
10. Shell Programming and Scripting
I'm trying to do something like this:
find . -name blablabla -exec ln -s ./"{:53:14} blablabla" \;
The idea is find blablabla and create a symbolic link to it using part of it's path and then it's name, "blablabla."
I just don't know if I can call characters out of a find variable. ... (16 Replies)
Discussion started by: scribling
16 Replies
LEARN ABOUT SUNOS
sigstack
sigstack(3UCB) SunOS/BSD Compatibility Library Functions sigstack(3UCB)
NAME
sigstack - set and/or get signal stack context
SYNOPSIS
/usr/ucb/cc [ flag ... ] file ...
#include <signal.h>
int sigstack( nss, oss);
struct sigstack *nss, *oss;
DESCRIPTION
The sigstack() function allows users to define an alternate stack, called the "signal stack", on which signals are to be processed. When a
signal's action indicates its handler should execute on the signal stack (specified with a sigvec(3UCB) call), the system checks to see if
the process is currently executing on that stack. If the process is not currently executing on the signal stack, the system arranges a
switch to the signal stack for the duration of the signal handler's execution.
A signal stack is specified by a sigstack() structure, which includes the following members:
char *ss_sp; /* signal stack pointer */
int ss_onstack; /* current status */
The ss_sp member is the initial value to be assigned to the stack pointer when the system switches the process to the signal stack. Note
that, on machines where the stack grows downwards in memory, this is not the address of the beginning of the signal stack area. The
ss_onstack member is zero or non-zero depending on whether the process is currently executing on the signal stack or not.
If nss is not a null pointer, sigstack() sets the signal stack state to the value in the sigstack() structure pointed to by nss. If nss is
a null pointer, the signal stack state will be unchanged. If oss is not a null pointer, the current signal stack state is stored in the
sigstack() structure pointed to by oss.
RETURN VALUES
Upon successful completion, 0 is returned. Otherwise, -1 is returned and errno is set to indicate the error.
ERRORS
The sigstack() function will fail and the signal stack context will remain unchanged if one of the following occurs.
EFAULT Either nss or oss points to memory that is not a valid part of the process address space.
SEE ALSO
sigaltstack(2), sigvec(3UCB), signal(3C)
WARNINGS
Signal stacks are not "grown" automatically, as is done for the normal stack. If the stack overflows unpredictable results may occur.
NOTES
Use of these interfaces should be restricted to only applications written on BSD platforms. Use of these interfaces with any of the system
libraries or in multi-threaded applications is unsupported.
SunOS 5.10 22 Jan 1997 sigstack(3UCB)