SigSegV during stack unwind (AIX)


 
Thread Tools Search this Thread
Top Forums Programming SigSegV during stack unwind (AIX)
# 1  
Old 09-07-2008
SigSegV during stack unwind (AIX)

Hi
I am getting a strange segmentation fault during the unwind
process. I am trying to throw an object of an Exception class.
During the DoThrow (in libC.a) the stack starts growing until a
Signal is received.
The object thrown is of a class that inherits from a common class,
and the signal only appears rarely - but consistently when it does appear.

I am useing xlC V8 on Aix 5.3 . Dod anyone experience/heard of something like this ? Could it be a copiler problem ?

Thanks
Login or Register to Ask a Question

Previous Thread | Next Thread

8 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Kernel Stack vs User Mode Stack

Hi, I am new to the linux kernel development area. I want to know what is the difference between kernel mode stack and user mode stack? Does each process has a user mode stack and a kernel mode stack?? Or Each process has a user mode stack and there is only one kernel mode stack that is shared by... (4 Replies)
Discussion started by: saurabhkoar
4 Replies

2. Programming

SIGSEGV when allocate a certain size

The problem: I need to work with large arrays and after one of my structures grew in size my program started getting segmentation fault. My code where I allocate the arrays: static R1 *tarr; static R2 *rarr; proc_init_mem() { const int t_sz = sizeof(R1) *... (9 Replies)
Discussion started by: migurus
9 Replies

3. UNIX for Advanced & Expert Users

How to create SIGSEGV at particular memory?

Hi I want to create a SIGSEGV when program tries to access one particular area in memory. Is this possible. If so whats the command. (4 Replies)
Discussion started by: jionnet
4 Replies

4. Solaris

sigsegv Fault

I receive a sigsegv failure. I was under the impression that a core file is created everytime a sigsegv occurrs and the process is terminated. I have had two recent occurrances of a core file not being created. Does anyone know why a core file would not be created. (2 Replies)
Discussion started by: amp4cats
2 Replies

5. AIX

Received signal #11, SIGSEGV [default] on AIX 6.1

Hello, One of our customer is getting segmentation fault when he runs his shell script which invokes our executable on AIX 6.1. On AIX 5.3, there were no issues. Here is the truss output. 811242: __loadx(0x0A040000, 0xF0D3A26C, 0x00000000, 0x00000009, 0x00000000) = 0xF026E884... (0 Replies)
Discussion started by: erra_krishna
0 Replies

6. UNIX and Linux Applications

SIGSEGV Signal handling

Hello, Can anybody tell me how can i handle segmentation fault signal, in C code? (2 Replies)
Discussion started by: mustus
2 Replies

7. Programming

SIGSEGV, Segmentation fault

Here is my initiating code: #define NUM 20 static struct tab { int count; int use; } tab; int curtab = 0; int tab_create(int tab_count) { curtab++; tab.use = 1; tab.count = tab_count; kprintf("here!"); return curtab; } (2 Replies)
Discussion started by: micmac700
2 Replies

8. Programming

SIGSEGV problem

Hi. Can someone to help me in a segfault problem? I have a big C++ program that crash from time to time because it receive the SIGSEGV signal. So my question is: Can I find, without using gdb or other debugging tools, which line from source code cause that problem? Or if exist some gdb API... (1 Reply)
Discussion started by: vaidac_coder
1 Replies
Login or Register to Ask a Question
U_STACK_TRACE(3X)														 U_STACK_TRACE(3X)

NAME
U_STACK_TRACE(), _UNW_STACK_TRACE() - produce a trace back of the procedure call stack using the unwind library SYNOPSIS
DESCRIPTION
prints a formatted stack trace to standard error. produces a formatted stack trace on the output stream indicated by parameter out_file. The stream must be a writable stream for output to be produced. APPLICATION USAGE
and are thread-safe. They are not async-cancel-safe because they make use of which is not async-cancel-safe. A cancellation point may occur when a thread is executing RETURN VALUE
None ERRORS
can fail to give the entire stack back trace under the following conditions: o Low memory conditions. The unwind library is not able to allocate enough memory to perform the tasks of tracking back over the stack or of looking up symbols names associated with instruction pointer addresses encountered. o Executables and shared libraries that fail to conform to the Runtime Architecture for Itanium-based systems. For example, they may have invalid, incomplete, or missing unwind tables; or invalid or incorrect unwind information blocks. EXAMPLES
Given the following C program: Compiling and executing the program produces output similar to this: AUTHOR
was developed by HP. SEE ALSO
_UNW_createContextForSelf(3X), _UNW_currentContext(3X), _UNW_getGR(3X), unwind(5). Itanium(R)-based System Only U_STACK_TRACE(3X)