np,
just a formatting suggestion to help you cut down from having to type so much redundant code.
, in your main, putting the print out options message in only once, just after your...
Type: Posts; User: poorboy
np,
just a formatting suggestion to help you cut down from having to type so much redundant code.
, in your main, putting the print out options message in only once, just after your...
in your functions SetupReverse()
printf("Please input a sentence: \n");
// stops it dead cold.
getchar();
//gets the input you're looking for.
c = getchar();
maybe after all of them mistakes pointed out , I am putting your logic to question. your first check is for if list Not Null then return , causing it to leave your function,
then here,
...
really you are still arguing with me about this? really?
it is all within the first three post, post 1, everything, post 2 the accusation that actually came from you,
post 3 me clarifying it...
it is exactly not the reason it seg fautled in the first place. Because it was not even there when it seg faulted in the first place.
SO it cannot by any means be the reason that it seg fault ,...
the printf in MAIN were not the cause of the seg fault, that is what I am and have been saying all along, BECAUSE it was seg faulting before that, as I have stated, therefore it was not the reason,...
you do not even understand the basic fundamentals of what "name calling is" making you ignorant of the facts. in fact the printf in question were not what was causing it to seg fault, again you are...
well nevertheless, it is not in the actual code being put into "production" and I'll remember to not printf as I did in listdir for a char**
not bad for a ass hole brainsead idiot , which my act...
yes that was to the one that called me an a(ss) hole, braindead idiot for no good reason,
not the ones put into question and my post above expline something went strange because it is not seg...
In listdir function, thanks, let me go back and look at that .
Now I am more confused then before. I compiled it again,
gcc -wall filename.c
ran it still leaving in the printf
so you're the brain around here, then explain to me HOW, when something takes place before something else takes place. One can say with absolute certainly that is was what took place after the first...
that is a valid statement, but it still does not explain why it is seg faulting when no printf is in there on either side of malloc. is this not a valid malloc call?
char **names;
int sum = 10;...
now your resorting to name calling? no it is not your insults are being reported.
yes I do need global variables , that is completely irrelevant to this seg fault, for your information to set you mind at ease, this is being used in another program where I have to declared them...
why does it seg fault when I use malloc, and it does not seg fault using calloc , rather, when using calloc I can read in
find /media/data1/HPImages -type f | wc -l
109728
files without...
I completely understand all of that, but this was not a add every printf all at once procedure that I did, the overs above the malloc were added first one at a time, for each run checking to see what...
go back up and read my post, every error is what I suggest you look up, into . plus maybe look into how to use fscan in conjunction with sscan when using a loop checking for eof. other wise figure...
yours
readPolygon.c(53): error #165: too few arguments in function call
fgets (record, filepointer);
the definition for fgets
char *fgets(char *str, int n, FILE *stream)
what pram are...
how so? the printf are to locate when it is happening. it seg faulted somewhere, that wittled it down to the where. because it was not getting past the malloc
path = strdup(argv[2]); ...
all of them printf's came after it already was blowing up (seg faulting). I changed it to
names = (char**) calloc(num, sizeof(char*));
The calloc() function shall allocate unused space for an...
this was working yesterday, when i came back today to use it to figure out some more stuff, it is now giving me a segfault. I hope all of this code is not too much, but so one can see what is going...