Sponsored Content
Full Discussion: Hi! segmentation fault
Top Forums Programming Hi! segmentation fault Post 302095992 by jim mcnamara on Monday 13th of November 2006 08:05:44 AM
Old 11-13-2006
Most C compilers are going to issue errors/warnings with your code. You have some problems.

First suggestion to fix one issue - #include <limits.h>

Usually dealing with full filenames means declare your strings like this with PATH_MAX
Code:
   char mydir[PATH_MAX]={0x0};

Plus, what you're doing is far easier with ftw() - see man ftw
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Segmentation Fault

hello all, I tried a program on an array to intialise array elements from the standard input device.it is an integer array of 5 elements.but after entering the 4th element it throws a message called "Segmentation Fault" and returns to the command prompt without asking for the 5th element. ... (3 Replies)
Discussion started by: compbug
3 Replies

2. Programming

segmentation fault

ive written my code in C for implementation of a simple lexical analyser using singly linked list hence am making use of dynamic allocation,but when run in linux it gives a segmentation fault is it cause of the malloc function that ive made use of????any suggestions as to what i could do??? thank... (8 Replies)
Discussion started by: rockgal
8 Replies

3. AIX

Segmentation fault

Hi , During execution a backup binary i get following error "Program error 11 (Segmentation fault), saving core file in '/usr/datatools" Riyaz (2 Replies)
Discussion started by: rshaikh
2 Replies

4. Programming

Why not a segmentation fault??

Hi, Why I don't receive a segmentation fault in the following sample. int main(void) { char buff; sprintf(buff,"Hello world"); printf("%s\n",buff); } If I define a buffer of 10 elements and I'm trying to put inside it twelve elements, Should I receive a sigsev... (22 Replies)
Discussion started by: lagigliaivan
22 Replies

5. UNIX for Dummies Questions & Answers

Segmentation Fault

Hi, While comparing primary key data of two tables thr bteq script I am getting this Error. This script is a shell script. *** Error: The following error was encountered on the output file. Script.sh: 3043492 Segmentation fault(coredump) Please let me know how to get through it. ... (5 Replies)
Discussion started by: monika
5 Replies

6. Programming

segmentation fault

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

7. Programming

Using gdb, ignore beginning segmentation fault until reproduce environment segmentation fault

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

8. Homework & Coursework Questions

Segmentation Fault

this is a network programming code to run a rock paper scissors in a client and server. I completed it and it was working without any error. After I added the findWinner function to the server code it starts giving me segmentation fault. -the segmentation fault is fixed Current problem -Also... (3 Replies)
Discussion started by: femchi
3 Replies

9. Programming

Segmentation fault

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

10. Programming

C. To segmentation fault or not to segmentation fault, that is the question.

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
FTW(3)							   BSD Library Functions Manual 						    FTW(3)

NAME
ftw, nftw -- traverse (walk) a file tree SYNOPSIS
#include <ftw.h> int ftw(const char *path, int (*fn)(const char *, const struct stat *ptr, int flag), int depth); int nftw(const char *path, int (*fn)(const char *, const struct stat *ptr, int flag, struct FTW *), int depth, int flags); DESCRIPTION
These functions are provided for compatibility with legacy code. New code should use the fts(3) functions. The ftw() and nftw() functions traverse (walk) the directory hierarchy rooted in path. For each object in the hierarchy, these functions call the function pointed to by fn. The ftw() function passes this function a pointer to a NUL-terminated string containing the name of the object, a pointer to a stat structure corresponding to the object, and an integer flag. The nftw() function passes the aforementioned argu- ments plus a pointer to a FTW structure as defined by <ftw.h> (shown below): struct FTW { int base; /* offset of basename into pathname */ int level; /* directory depth relative to starting point */ }; Possible values for the flag passed to fn are: FTW_F A regular file. FTW_D A directory being visited in pre-order. FTW_DNR A directory which cannot be read. The directory will not be descended into. FTW_DP A directory being visited in post-order (nftw() only). FTW_NS A file for which no stat(2) information was available. The contents of the stat structure are undefined. FTW_SL A symbolic link. FTW_SLN A symbolic link with a non-existent target (nftw() only). The ftw() function traverses the tree in pre-order. That is, it processes the directory before the directory's contents. The depth argument specifies the maximum number of file descriptors to keep open while traversing the tree. It has no effect in this imple- mentation. The nftw() function has an additional flags argument with the following possible values: FTW_PHYS Physical walk, don't follow symbolic links. FTW_MOUNT The walk will not cross a mount point. FTW_DEPTH Process directories in post-order. Contents of a directory are visited before the directory itself. By default, nftw() traverses the tree in pre-order. FTW_CHDIR Change to a directory before reading it. By default, nftw() will change its starting directory. The current working directory will be restored to its original value before nftw() returns. RETURN VALUES
If the tree was traversed successfully, the ftw() and nftw() functions return 0. If the function pointed to by fn returns a non-zero value, ftw() and nftw() will stop processing the tree and return the value from fn. Both functions return -1 if an error is detected. ERRORS
The ftw() and nftw() functions may fail and set errno for any of the errors specified for the library functions close(2), open(2), stat(2), malloc(3), opendir(3) and readdir(3). If the FTW_CHDIR flag is set, the nftw() function may fail and set errno for any of the errors speci- fied for chdir(2). In addition, either function may fail and set errno as follows: [EINVAL] The depth argument is less than 1 or greater than OPEN_MAX. LEGACY ERRORS
The ftw() and nftw() functions are far more tolerant of symlink cycles and are lax in reporting errors while accessing the initial path. When nftw() is passed FTW_MOUNT, it will pass the mount point to the callback function. SEE ALSO
chdir(2), close(2), open(2), stat(2), fts(3), malloc(3), opendir(3), readdir(3), compat(5) STANDARDS
The ftw() and nftw() functions conform to IEEE Std 1003.1-2001 (``POSIX.1'') and Version 3 of the Single UNIX Specification (``SUSv3''). HISTORY
Prior to MacOS X 10.4 ftw did not follow symlinks. BUGS
The depth argument is currently ignored. BSD
May 20, 2003 BSD
All times are GMT -4. The time now is 10:35 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy