10-20-2010
I don't want to correct everything....
main is NOT void, it is int. Return to int from main(). Always.
Turn on warnings and every other diagnostic known to the compiler.
Strings in C cannot be less than two characters, if they contain dat. a[1] will not fly generally. Why? they need a terminating nul characters \0 == ascii 0
you do not have all of the #include files required to compile the code.
Read the man page for read & open - it tells you at the top the name of the include file(s)required.
You cannot call a compile ok until:
1. there are zero warnings
2. there are zero errors
Period. Anything else that seems to work is a disaster waiting to happen.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hello To All!
Now anfd then I receive a message on my console:
Segmentation fault (core dumped)
What does it mean? Or more precisely what are the implications?
:confused: (1 Reply)
Discussion started by: Ivo
1 Replies
2. Programming
what r the situations to receive an error msg like the one below
Segmentation Fault (core dumped) (2 Replies)
Discussion started by: bankpro
2 Replies
3. UNIX for Advanced & Expert Users
I use SCO UNIX 5.07 on a Compaq Proliant Machine. Each time I press the Escape or Delete key while running a program or issuing a FoxBase+ command from the dot prompt, I receive the error message: "Memory Fault - Core Dumped" and the screen locks up immediately.
I would appreciate if necessary... (0 Replies)
Discussion started by: bayuz
0 Replies
4. Programming
I have written a code in UNIX which is complied by using g++. Compling with turbo C didnt yield any errors, but with g++ I am getting Memory fault, core dumped. Could anyone help me out with this?
Given below is the code:
#include<stdio.h>
#include<string.h>
#include<stdlib.h>... (2 Replies)
Discussion started by: usshell
2 Replies
5. Solaris
i am getting Segmentation Fault (core dumped) on solaris,
but when i run the same program with same input on linux it runs successfully.
How can i trace the fault in program on solaris. (6 Replies)
Discussion started by: junaid.nehvi
6 Replies
6. Solaris
i am getting segmentation fault (core dumped)
i tried following things but couldn't understand what is wrong with my prog and where the problem is....
i have only adb debugger available on solaris....
so plz help
bash-3.00$ pstack core
core 'core' of 765: ./mod_generalised_tapinread... (4 Replies)
Discussion started by: junaid.nehvi
4 Replies
7. Red Hat
Hi All,
I am getting "Segmentation fault (core dumped)" error in the runtime. I am new this please can you tell me why is that i am getting this error and I am not sure of my compilation :
gcc -c avc_test.c
gcc -c md5.c
gcc avc_test.o md5.o -shared -Llibcoreavc_sdk.so -o proj
... (1 Reply)
Discussion started by: fido.genial
1 Replies
8. Programming
i am executing following program
int main()
{ char str;
FILE * fp;
int i=0; ... (4 Replies)
Discussion started by: bhavesh.sapra
4 Replies
9. UNIX for Advanced & Expert Users
When I was trying to mirror in my v880 server after OS up gradation from 8 to 10
metadb -afc 3 /dev/dsk/c1t1d0s7
I got an error
metadb: Segmentation Fault
Segmentation Fault (core dumped)
Then I logged a case to Oracle/sun team they suggest
"Please could you try
metadb -ac 3... (0 Replies)
Discussion started by: taherahmed
0 Replies
10. Programming
When I run programm show this message: Memory Fault (core dumped)
Does anyone can help me and tell me what is wrong? please
#include <stdlib.h>
#include <stdio.h>
#include <process.h>
#include <unistd.h>
#include <sys/types.h>
#include <sys/wait.h>
int main(int argc, char *argv) { ... (3 Replies)
Discussion started by: ebasse2
3 Replies
LEARN ABOUT DEBIAN
podchecker
PODCHECKER(1) Perl Programmers Reference Guide PODCHECKER(1)
NAME
podchecker - check the syntax of POD format documentation files
SYNOPSIS
podchecker [-help] [-man] [-(no)warnings] [file ...]
OPTIONS AND ARGUMENTS
-help Print a brief help message and exit.
-man Print the manual page and exit.
-warnings -nowarnings
Turn on/off printing of warnings. Repeating -warnings increases the warning level, i.e. more warnings are printed. Currently
increasing to level two causes flagging of unescaped "<,>" characters.
file The pathname of a POD file to syntax-check (defaults to standard input).
DESCRIPTION
podchecker will read the given input files looking for POD syntax errors in the POD documentation and will print any errors it find to
STDERR. At the end, it will print a status message indicating the number of errors found.
Directories are ignored, an appropriate warning message is printed.
podchecker invokes the podchecker() function exported by Pod::Checker Please see "podchecker()" in Pod::Checker for more details.
RETURN VALUE
podchecker returns a 0 (zero) exit status if all specified POD files are ok.
ERRORS
podchecker returns the exit status 1 if at least one of the given POD files has syntax errors.
The status 2 indicates that at least one of the specified files does not contain any POD commands.
Status 1 overrides status 2. If you want unambiguous results, call podchecker with one single argument only.
SEE ALSO
Pod::Parser and Pod::Checker
AUTHORS
Please report bugs using <http://rt.cpan.org>.
Brad Appleton <bradapp@enteract.com>, Marek Rouchal <marekr@cpan.org>
Based on code for Pod::Text::pod2text(1) written by Tom Christiansen <tchrist@mox.perl.com>
perl v5.14.2 2014-09-30 PODCHECKER(1)