Mysterious error

Okay so I can't post all the code for this but I would like to describe a problem that I am having and see if anyone has any ideas what the cause could be. I have a program which has a large loop in which it creates fills in integer strings in structures. I then take the last value from each of these strings and place it into an array because I have to overwrite the old strings but need the last value of the string later. in the end this results in an array of size [32][1000] because it has saved in it the terminal results of 32 different strings from 1000 runs of the loop. The values are set into the array correctly which I have verified. Later, after having never having done anything to the array since I put in the values I print the values from it to a file. The results are almost all correct except for one strange problem. For the first row of the array ([0][0] to [0][999]) I get about 10 correct values, then about 70 values which are all 0 (I checked that when the values were first put into the array the were NOT 0's), then about 20 more correct numbers, then another 70 or so 0's, and then correct numbers until the end of the row. All other rows of the array are completely correct. Can anyone think of a possible cause for this strange pattern?

Let me check:

Seer? Nope, on mystical drugs.
Crystal Ball? Nope, cloudy today.
Prophet? Nope, not talking to God this morning.

Guess you'll have to post up at least the code for that loop - something as simple as possible, but shows the problem, would be A-1.

Quote:

---

Originally Posted by deeisenberg

Can anyone think of a possible cause for this strange pattern?

---

Illegal memory accesses resulting in undefined behaviour?

a bug in your program?

Okay, so things have gotten even weirder but I have located the spot where the data loss occurs.

Code:

---

            matrix[0][19]=matrix[0][19];
            for(ri=0; ri<2000; ri++) ran[ri]=genrand_int32();
            ri=0;
            b[0].trait[0]=1;
            b[1].trait[0]=1;
            for(bi=0; bi<64; bi++) for(i=0; i<74; i++) b[bi].counter[i]=0;
            for(i=1; i<74; i++) { /*Sim along b1*/
                if(b[0].trait[i-1]) {
                    b[0].trait[i]=gen();
                    if(!b[0].trait[i]) b[0].counter[i+1]++;
                }
                else {
                    b[0].trait[i]=rev(b[0].counter[i], ii);
                    if(!b[0].trait[i]) b[0].counter[i+1]=b[0].counter[i]+1;
                }
            }
            matrix[0][19]=matrix[0][19];

---

At the beginning of this section of code matrix[0][19]=1. At the end matrix[0][19]=0.

This is all within the main loop which does most of the work in my program. The array matrix is local.

Quote:

---

Originally Posted by QuantumPete

Illegal memory accesses resulting in undefined behaviour?

---

My vote is this.

Tim S.

Without all your array and struct declarations as well, there isn't a lot we could say.

Array overrun seems as good a bet as any.

The array isn't overrun because it happens within that section of code in one run. The declarations were...

Code:

---

        int matrix[32][2000]; /*Terminal character states*/
        struct branch { /*Branches*/
                char trait[74];
                int counter[75];
        }  b[62];

---

Quote:

---

Originally Posted by deeisenberg

The array isn't overrun because it happens within that section of code in one run. The declarations were...

Code:

---

        int matrix[32][2000]; /*Terminal character states*/
        struct branch { /*Branches*/
                char trait[74];
                int counter[75];
        }  b[62];

---

---

look at this

Code:

---

for(bi=0; bi<64; bi++) for(i=0; i<74; i++) b[bi].counter[i]=0;

---

there are only 62 b's
you access 64

mystery solved

Kurt