Developer forums (C::B DEVELOPMENT STRICTLY!) > Development
Help reading codeblocks.RPT
daniloz:
--- Quote from: ollydbg on June 15, 2012, 09:24:16 am ---Ok, it looks like this code does not crash c::b on you win7 system. (Win7 is robust than WinXP)
What I can suggest is you can write to some other address:
--- Code: ---char * p = anyIntValue;
*p = 0;
--- End code ---
Then, change anyIntValue until your c::b crashed, or you just do a loop like:
--- Code: ---for (int i=0;i<0xfffffffffff;i++)
{
char * p = i;
*p = 0;
}
--- End code ---
--- End quote ---
Actually, your original code is fine and even if I do the for, when debugging, I get a "segmentation fault" on the first iteration, i.e. with char *p = 0. The strange thing is that after this "segmentation fault" I can just run again and I come back to the "Start Here" window.
And, again, when not using the debugger, but just running it, I see no exception/crash at all...
ollydbg:
--- Quote from: daniloz on June 15, 2012, 09:37:52 am ---
--- Quote from: ollydbg on June 15, 2012, 09:24:16 am ---Ok, it looks like this code does not crash c::b on you win7 system. (Win7 is robust than WinXP)
What I can suggest is you can write to some other address:
--- Code: ---char * p = anyIntValue;
*p = 0;
--- End code ---
Then, change anyIntValue until your c::b crashed, or you just do a loop like:
--- Code: ---for (int i=0;i<0xfffffffffff;i++)
{
char * p = i;
*p = 0;
}
--- End code ---
--- End quote ---
Actually, your original code is fine and even if I do the for, when debugging, I get a "segmentation fault" on the first iteration, i.e. with char *p = 0. The strange thing is that after this "segmentation fault" I can just run again and I come back to the "Start Here" window.
And, again, when not using the debugger, but just running it, I see no exception/crash at all...
--- End quote ---
Interesting, you need more dirty crash code snippet like:
--- Code: ---delete p; //p can be any address
--- End code ---
Navigation
[0] Message Index
[*] Previous page
Go to full version