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
sigstack(2)							System Calls Manual						       sigstack(2)

Name
       sigstack - set or get signal stack context

Syntax
       #include <signal.h>

       struct sigstack {
       caddr_t	 ss_sp;
       int  ss_onstack;
       };

       sigstack(ss, oss)
       struct sigstack *ss, *oss;

Description
       The  system  call  allows users to define an alternate stack on which signals are to be processed.  If ss is nonzero, it specifies a signal
       stack on which to deliver signals and tells the system if the process is currently executing on that stack.  When a signal's  action  indi-
       cates  its handler should execute on the signal stack (specified with a call), the system checks to see if the process is currently execut-
       ing 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.  If oss is nonzero, the current signal stack state is returned.

       Signal stacks are not grown'automatically, as is done for the normal stack.  If the stack overflows, unpredictable results may occur.

Return Values
       Upon successful completion, a value of zero (0) is returned.  Otherwise, a value of -1 is returned and errno is set to indicate the error.

Diagnostics
       The system call fails and the signal stack context remains unchanged, if one of the following occurs.

       [EFAULT]       Either ss or oss points to memory that is not a valid part of the process address space.

See Also
       sigvec(2), setjmp(3)

																       sigstack(2)