12-06-2011
I can't see your computer from here. Please post your code.
Almost certainly it's overrunning the end of the array or otherwise corrupting memory in ways that don't always crash the program.
10 More Discussions You Might Find Interesting
1. Programming
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
2. Programming
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
3. Solaris
Hello - I am finding difficulty in creating and allocating correct size to File Systems on solarix x86 box. Please see below contents I followed on screen and in the end It shows that /app file system is created of size 135GB , I wanted it to be 30gb as mentioned during 'format' command in 'Enter... (7 Replies)
Discussion started by: panchpan
7 Replies
4. Programming
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... (0 Replies)
Discussion started by: barak
0 Replies
5. Programming
i wrote handler for sigsegv such that i can allocate memory for a variable to which
sigsegv generated for illlegal acces of memory.
my code is
#include <signal.h>
#include<stdio.h>
#include<stdlib.h>
#include<string.h>
char *j;
void segv_handler(int dummy)
{
j=(char *)malloc(10);
... (4 Replies)
Discussion started by: pavan6754
4 Replies
6. UNIX and Linux Applications
Hello,
Can anybody tell me how can i handle segmentation fault signal, in C code? (2 Replies)
Discussion started by: mustus
2 Replies
7. AIX
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
8. Solaris
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
9. Shell Programming and Scripting
While running script I am getting an error like
Few lines in data are not being processed.
After googling it I came to know that adding such line would give some memory to it
ini_set("memory_limit","64M");
my input file size is 1 GB.
Is that memory limit is based on RAM we have on... (1 Reply)
Discussion started by: elamurugu
1 Replies
10. UNIX for Advanced & Expert Users
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
LEARN ABOUT CENTOS
allegro_exit
allegro_exit(3alleg4) Allegro manual allegro_exit(3alleg4)
NAME
allegro_exit - Closes down the Allegro system.
SYNOPSIS
#include <allegro.h>
void allegro_exit();
DESCRIPTION
Closes down the Allegro system. This includes returning the system to text mode and removing whatever mouse, keyboard, and timer routines
have been installed. You don't normally need to bother making an explicit call to this function, because allegro_init() installs it as an
atexit() routine so it will be called automatically when your program exits.
Note that after you call this function, other functions like destroy_bitmap() will most likely crash. This is a problem for C++ global
destructors, which usually get called after atexit(), so don't put Allegro calls in them. You can write the destructor code in another
method which you can manually call before your program exits, avoiding this problem.
SEE ALSO
install_allegro(3alleg4), allegro_init(3alleg4), destroy_bitmap(3alleg4), ex3d(3alleg4), exscn3d(3alleg4), exswitch(3alleg4),
exxfade(3alleg4), exzbuf(3alleg4)
Allegro version 4.4.2 allegro_exit(3alleg4)