02-02-2011
Hi ,
OS : HP-UX
compiler : gcc
Regards,
Kiran
10 More Discussions You Might Find Interesting
1. Programming
sometimes for this code i get a segmentation fault for codes llike this
:
int main{
int * a= 0;
int b;
a = (int*)malloc(sizeof(int));
///some code using these variable but no freeing of a
if(a){
free(a);
a = 0;
}
return... (3 Replies)
Discussion started by: wojtyla
3 Replies
2. Programming
I have written a program which takes a directory as command line arguments and displays all the dir and files in it.
I don't know why I have a problem with the /etc directory.It displays all the directories and files untill it reaches a sub directory called peers which is in /etc/ppp/peers.the... (4 Replies)
Discussion started by: vijlak
4 Replies
3. Programming
If I do this.
Assume
struct life
{
char *nolife;
}
struct life **life;
// malloc initialization & everything
if(life->nolife == 0)
Would I get error at life->nolife if it is equal to 0.
wrong accession? (3 Replies)
Discussion started by: joey
3 Replies
4. AIX
Hello,
I am running on a AIX5.2 server with Oracle 10g and 9i. My code compiles and works fine in 32-bit mode. The
same code compiles in 64-bit and runs good. The program catches CNTRL-C signal to terminate. Only on 64-bit code
when i hit CNTRL-C, the program exits with segmentation... (0 Replies)
Discussion started by: sumesh0710
0 Replies
5. Programming
Hi,
I am having this segmentation fault not in the following program, bt. in my lab program . My lab program is horrible long so cannot post it here bt. I am using the following logic in my program which is giving the segmentation fault. Bt. if I run this sample program as it is it dosen't give... (3 Replies)
Discussion started by: mind@work
3 Replies
6. Programming
I use a binary name (ie polo) it gets some parameter , so for debugging normally i do this :
i wrote script for watchdog my app (polo) and check every second if it's not running then start it , the problem is , if my app , remain in state of segmentation fault for a while (ie 15 ... (6 Replies)
Discussion started by: pooyair
6 Replies
7. Programming
#include<stdlib.h>
#include <pthread.h>
#include "tlpi_hdr.h"
#include <stdio.h>
static volatile int glob = 0;
static struct {
pthread_t t1,t2;
} *thread;
static void * /* Loop 'arg' times incrementing 'glob' */
threadFunc(void *arg)
{
int loops = *((int *) arg); ... (1 Reply)
Discussion started by: fwrlfo
1 Replies
8. Programming
I keep getting this fault on a lot of the codes I write, I'm not exactly sure why so I'd really appreciate it if someone could explain the idea to me.
For example this code
#include <stdio.h>
main()
{
unsigned long a=0;
unsigned long b=0;
int z;
{
printf("Enter two... (2 Replies)
Discussion started by: sizzler786
2 Replies
9. Programming
Oddities with gcc, 2.95.3 for the AMIGA and 4.2.1 for MY current OSX 10.14.1...
I am creating a basic calculator for the AMIGA ADE *NIX emulator in C as it does not have one.
Below are two very condensed snippets of which I have added the results inside the each code section.
IMPORTANT!... (11 Replies)
Discussion started by: wisecracker
11 Replies
10. Programming
Apologies for any typos...
Well guys, been researching 'goto' in C and they say that you can't 'goto' labels in another function as a segmentation fault will occur.
However I have found a way to 'goto' a label in another function that is NOT main() using the asm() function.
As you know I... (14 Replies)
Discussion started by: wisecracker
14 Replies
LEARN ABOUT FREEBSD
color.4th
COLOR.4TH(8) BSD System Manager's Manual COLOR.4TH(8)
NAME
color.4th -- FreeBSD color-detection boot module
DESCRIPTION
The file that goes by the name of color.4th is a set of commands designed to simplify color logic. The commands of color.4th by themselves
are not enough for most uses. Please refer to the examples below for the most common situations, and to loader(8) for additional commands.
Before using any of the commands provided in color.4th, it must be included through the command:
include color.4th
This line is present in /boot/loader.4th file, so it is not needed (and should not be re-issued) in a normal setup.
The commands provided by it are:
loader_color? Returns FALSE if the loader_color environment variable is set to ``NO'' (case-insensitive) or ``0''. Otherwise
returns TRUE (unless booting serial).
The environment variables that effect its behavior are:
loader_color
If set to ``NO'' (case-insensitive) or ``0'', causes loader_color? to return FALSE, indicating to many modules that color
should not be used.
FILES
/boot/loader The loader(8).
/boot/color.4th color.4th itself.
/boot/loader.rc loader(8) bootstrapping script.
EXAMPLES
Standard i386 /boot/loader.rc:
Use color where applicable:
loader_color="YES"
SEE ALSO
loader.conf(5), loader(8), loader.4th(8)
HISTORY
The color.4th set of commands first appeared in FreeBSD 9.0.
AUTHORS
The color.4th set of commands was written by Devin Teske <dteske@FreeBSD.org>.
BSD
August 6, 2013 BSD