11-04-2010
Hi
still have this problem here is more info :
strace output ( 3 last lines )
munmap(0x2aaaabb81000, 4096) = 0
--- SIGSEGV (Segmentation fault) @ 0 (0) ---
+++ killed by SIGSEGV (core dumped) +++
Im using RH 5 2.6.18-128.el5 < uname -a out put
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
help, what is the difference between core dump and panic dump? (1 Reply)
Discussion started by: aileen
1 Replies
2. Programming
MY friends:
my program under sco unix have a problem?
it create a core dump file on the path when execute program ,
but i can't find the error of the C program ,i don't know how to
see the error about my program use core, please help me
or give me some suggest and what tools can use... (1 Reply)
Discussion started by: zhaohaizhou
1 Replies
3. Shell Programming and Scripting
Hello,
I host a couple of Call of Duty gameing servers. There are some hackers who love the crash them. When they crash them it simply causes a segmentaion fault and kills the PID. I was wondering it you could help me write a script to simply restart the program after it has been crashed. The... (9 Replies)
Discussion started by: Phobos
9 Replies
4. UNIX for Dummies Questions & Answers
Hi All
I am new for this forum. I have a core file by using gdb and bt cmd I got the function name but I want to the exact cause of the core dump because of I can not reproduse the binary so if any one know the cmd plz plz plz let me know. (0 Replies)
Discussion started by: gyanusoni
0 Replies
5. UNIX for Dummies Questions & Answers
We have an application that terminates with segmentation violation errors in the logs. No source code is available since this is a third party software that is way past its maintenance life cycle. Under these circumstances is there a way to force a core dump of the process for further analysis??
... (3 Replies)
Discussion started by: Un1xNewb1e
3 Replies
6. AIX
Hi ,
I want to read core dump file on AIX5.3. While i am trying to use following commands, i am getting only few lines of information.
ux201p3:e46123> dbx capsWrkstnMgr core
Type 'help' for help.
reading symbolic information ...
Segmentation fault in malloc_common.extend_brk at... (1 Reply)
Discussion started by: rps
1 Replies
7. Linux
Hi everybody,
I want to find out all the processes that ran before a server crashed. Is that possible?
I've looked in /var/log/messages and found out that the system was out of memory.
A user probably wrote a script (in Perl or Python) that used up all available memory and crashed the... (11 Replies)
Discussion started by: z1dane
11 Replies
8. UNIX for Dummies Questions & Answers
I have come into a business environtment problem and had been 10+ years since the last time I did any unix admin work.
A long time ago some mainframe person created an app that talked to a mainframe on UNIX and wrote a c program with "core" in the file name to indicate that the file was the... (2 Replies)
Discussion started by: pcooke2002
2 Replies
9. Red Hat
Hello All,
I am new joiner of this forum.I am new to Linux shell scripting.
At present I have identified 1 application which stalls very frequently (PID is say xyz) and I am not having much information in its application log to identify the root cause of stalling. I need to take the core dump... (19 Replies)
Discussion started by: Anjan Ganguly
19 Replies
LEARN ABOUT SUNOS
_stack_grow
_stack_grow(3C) Standard C Library Functions _stack_grow(3C)
NAME
_stack_grow - express an intention to extend the stack
SYNOPSIS
#include <ucontext.h>
void *_stack_grow(void *addr);
DESCRIPTION
The _stack_grow() function indicates to the system that the stack is about to be extended to the address specified by addr. If extending
the stack to this address would violate the stack boundaries as retreived by stack_getbounds(3C), a SIGSEGV is raised.
If the disposition of SIGSEGV is SIG_DFL, the process is terminated and a core dump is generated. If the application has installed its own
SIGSEGV handler to run on the alternate signal stack, the signal information passed to the handler will be such that a call to stack_viola-
tion(3C) with these parameters returns 1.
The addr argument is a biased stack pointer value. See the Solaris 64-bit Developer's Guide.
This function has no effect if the specified address, addr, is within the bounds of the current stack.
RETURN VALUES
If the _stack_grow() function succeeds and does not detect a stack violation, it returns addr.
ERRORS
No errors are defined.
USAGE
The _stack_grow() function does not actually adjust the stack pointer register. The caller is responsible for manipulating the stack
pointer register once _stack_grow() returns.
The _stack_grow() function is typically invoked by code created by the compilation environment prior to executing code that modifies the
stack pointer. It can also be used by hand-written assembly routines to allocate stack-based storage safely.
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Interface Stability |Evolving |
+-----------------------------+-----------------------------+
|MT-Level |Async-Signal-Safe |
+-----------------------------+-----------------------------+
SEE ALSO
stack_getbounds(3C), stack_inbounds(3C), stack_violation(3C), attributes(5)
Solaris 64-bit Developer's Guide
SunOS 5.10 18 Jul 2002 _stack_grow(3C)