Sponsored Content
Top Forums Programming readdir and dynamic array memory corruption Post 302491544 by DreamWarrior on Thursday 27th of January 2011 05:25:43 PM
Old 01-27-2011
UGH...way beaten to the punch, lol...that's what happens when I start typing a response, go into a meeting and come back to finish it up...haha...at least we're all telling you the same thing.
 

10 More Discussions You Might Find Interesting

1. Programming

Creating an array to hold posix thread ids: Only dynamic array works

I am facing a strange error while creating posix threads: Given below are two snippets of code, the first one works whereas the second one gives a garbage value in the output. Snippet 1 This works: -------------- int *threadids; threadids = (int *) malloc (num_threads * sizeof(int)); ... (4 Replies)
Discussion started by: kmehta
4 Replies

2. UNIX for Dummies Questions & Answers

'memory corruption' error when using Awk

Hello, everyone. I got the following error when I am using awk to analysis some text file: *** glibc detected *** awk: malloc(): memory corruption: 0x080c67f8 *** ======= Backtrace: ========= /lib/tls/i686/cmov/libc.so.6 /lib/tls/i686/cmov/libc.so.6... (5 Replies)
Discussion started by: kooyee
5 Replies

3. Programming

Why does this occur? *** glibc detected *** malloc(): memory corruption: 0x10013ff8 ***

there seems not to be error in this segment. In some computers, it can work well. But in others, it will give a failure. why it ocurrs and how to deal with it? in a function: if( *ver == NULL ) { *ver = (vertex *) malloc(sizeof(vertex)); //this line ... (17 Replies)
Discussion started by: cdbug
17 Replies

4. SCO

SCO openserver Dynamic linker corruption

Hi every body I have a problem like that "Dynamic linker error" message. I can't load many of programs in sco unix openserver 5.0.6. I guess this problem appear after my last effort to install "SCO Development System" package. How can I fix this problem? would you please help me ? (1 Reply)
Discussion started by: javad1_maroofi
1 Replies

5. Programming

./match_pattern.out: malloc(): memory corruption: 0x0000000013a11600 ***

Hi All, I have a simple code which does some computation by matching string patterns. In brief: 1. The code reads .dat and .txt files. 2. .dat files are huge text files and .txt files contain some important words. 3. I am just doing strstr to find the patterns. 4. The function returns the... (3 Replies)
Discussion started by: shoaibjameel123
3 Replies

6. Programming

*** glibc detected *** ./a.out: malloc(): memory corruption (fast):

*** glibc detected *** ./a.out: malloc(): memory corruption (fast): Posted A minute ago M trying to make multiway tree and dont know what happend when this part of code get executed: 01void ins(NODE *ptr) 02{ 03 //working 04 if(ptr!=NULL) 05 { 06 SNODE *var=NULL; 07 var=(SNODE... (3 Replies)
Discussion started by: exgenome
3 Replies

7. Programming

*** glibc detected *** : malloc(): memory corruption (fast)

Hi Friends, while executing the below code, am getting *** glibc detected *** ./ok: malloc(): memory corruption (fast) error, please suggest how to solve this issue. #include <stdio.h> #include <string.h> #include <sqlca.h> #include <alloca.h> /* Define constants for VARCHAR... (2 Replies)
Discussion started by: mpjobsrch
2 Replies

8. Programming

*** glibc detected *** ./a.out malloc() memory corruption

I am facing a problem of memory corruption. The loop runs for the first time but does not go through the second time. What could be the problem? for(int z=0;z<2;z++) { fp=fopen("poly.dat","r"); /*do something which reads this file into a 2D array*/ fclose(fp); ... (10 Replies)
Discussion started by: dare
10 Replies

9. Solaris

Solaris 10 Shared Memory Corruption with X11

I am having a problem with shared memory corruption. I have two 86 servers running Solaris 10 (150400-06). One of the servers is accessed by a Sun Ray thin client Version 11.1.3.0.2.6. I login into server one from the thin client. I then ssh -X to server two. When a process that contains a... (2 Replies)
Discussion started by: salerno
2 Replies

10. Programming

Memory corruption in dynamic array of strings

I put together a C function to add strings to a dynamic array of strings (mostly for educational purpose to explain pointers to my kid). It works, but sometimes one or two strings in the array becomes corrupted. Running example on 64 bit Ubuntu, gcc ver. 4.8.4 Hope my code is self-explanatory: ... (2 Replies)
Discussion started by: migurus
2 Replies
DIRECTORY(3)						     Library Functions Manual						      DIRECTORY(3)

NAME
directory, opendir, readdir, rewinddir, closedir, telldir, seekdir - directory routines SYNOPSIS
#include <sys/types.h> #include <dirent.h> DIR *opendir(const char *dirname) struct dirent *readdir(DIR *dirp) void rewinddir(DIR *dirp) int closedir(DIR *dirp) #define _MINIX 1 #include <sys/types.h> #include <dirent.h> long telldir(DIR *dirp) int seekdir(DIR *dirp, long pos) DESCRIPTION
These routines form a system independent interface to access directories. Opendir() opens the directory dirname and returns a pointer to this open directory stream. Readdir() reads one entry from the directory as a pointer to a structure containing the field d_name, a character array containing the null-terminated name of the entry. Rewinddir() allows the directory to be read again from the beginning. Closedir() closes the directory and releases administrative data. The Minix specific functions telldir() and seekdir() allow one to get the current position in the directory file and to return there later. Seekdir() may only be called with a position returned by telldir() or 0 (rewind). These functions should not be used in portable programs. SEE ALSO
dir(5). DIAGNOSTICS
Opendir() returns a null pointer if dirname can't be opened, or if it can't allocate enough memory for the DIR structure. Readdir() returns null if there are no more directory entries or on error. Closedir() and seekdir() returns 0 on success, -1 on error. Telldir() returns -1 on error. All of them set errno appropriately. Readdir() will only set errno on error, not on end-of-dir, so you should set errno to zero before- hand, and check its value if readdir() returns null. NOTES
The return value of readdir() needs to be copied before the next operation on the same directory if it is to be saved. AUTHOR
Kees J. Bot (kjb@cs.vu.nl) DIRECTORY(3)
All times are GMT -4. The time now is 07:05 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy