Thread: why error while the number is very big ?

>>ss = (char *) malloc(50000000);
Oh my goodness. You don't need that much memory. That's about 48 MB.

And I'm guessing that, if the source file is too big, you simply run out of memory.

And then goes the usual line: post the smallest simplest program that displays the problem.

Originally Posted by Elysia

>>ss = (char *) malloc(50000000);
Oh my goodness. You don't need that much memory. That's about 48 MB.

And I'm guessing that, if the source file is too big, you simply run out of memory.

And then goes the usual line: post the smallest simplest program that displays the problem.

Maybe the OP really does need that, whose to say? The one really bad thing about that, however, is the retval of malloc() was NOT checked.

EDIT: Oh, and another thing: If you are going to request that much memory it is best to keep in in PAGE_SIZE (usually a multiple of 4096).

Originally Posted by Kennedy

Maybe the OP really does need that, whose to say? The one really bad thing about that, however, is the retval of malloc() was NOT checked.

I question that, seriously, because it's allocated once for each row. And if the file is 1000 rows, are you going to allocate 46 GB then?

Ah yes, but the current code uses fscanf to read a... string. In a buffer 80 chars long. No wonder the code fails miserably. This is very prone to buffer overruns.
SourceForge.net: Buffer overrun - cpwiki
SourceForge.net: Scanf woes - cpwiki
Stick with fgets instead.

Probably not relate to your problems but I thought I'd point out some things...

#1.

Code:

while(!feof(fp))
{
    char line[80];//temporarily store line content
    int i = 0;
    unsigned long int len;
    //char tmp[80];
    //fgets(tmp,fp);
    fscanf(fp,"%s",line);

This method of controlling a loop is often done wrong as is the case here, rarely is it ever done correctly. The problem is that the flag that says you are at the end of the file only gets set after you attempt to read past the end of the file. When you read and process the last line of data from the file, feof is still false, you are at the end of file having read the last line but the indicator is still false. Because of this you'll enter your while loop one last time and attempt the read again (calling fscanf) which will fail - although this time it will set the end-of-file flag to true - leaving the buffer unchanged from the previously correct read. The effect of all this is that the last line of data will essentially be processed twice, something I'm guessing is not what you want to have happen in your program.

The 'better' way to handle this is to make the read operation a part of the while loops conditional check. In this case, the return value of the fscanf call can be checked to make sure data was read (or not). If not, the loop is never entered and no processing of bad data can take place. If the read is successful then the loop is entered and processed.

Code:

char line[80];//temporarily store line content

...

while(1 == fscanf(fp,"%s",line))
{
    int i = 0;
    unsigned long int len;
    ...

#2.

Code:

ss = (char *) malloc(...);

You shouldn't cast the return value from the malloc call in C.