Error accessing memory address 0x7816cd30: Input/output error.
I have totally disable my anti virus.
You don't know how happy that makes me, at this point, that someone else has been able to reproduce this damn error!
Do you have any suggestions for next step(s)?
the "memory access" error happens randomly, so I don't know how to check it. Does it due to GCC or GDB?
So far, on my system, it has been dependent on the location of the data file (but, apparently not for you?). I do not have the problem when the data file is in the project directory, but when it is located in (possibly specific) other folders. Since it is the same code (already compiled with a given compiler) that has the problem in one location, but not another, I'm leaning towards thinking it is the debugger.
-data file in parallel folder (up a level from the project file, then down a level into another folder) - the problem always occurs.
I can definitely confirm this!!!
I guess the problem is in GDB.
It would seem that this problem is limited to the Windows version. I just booted into Fedora 14 Linux (GNU gdb (GDB) Fedora (7.2-36.fc14) ) and could not recreate the problem with any of the test cases. Every 7.x version on the Windows side that I have tried can produce the problem.
search the string "Error accessing memory address" on the gdb's source, you can quickly find in "breakpoint.c" around line 1773. but I have no idea about everything else.
Also, the related topics can be discussed in GDB mailist(not here).
I am experiencing the very same problems. I see that the Bugzilla bug has not been worked on or even assigned to anyone in over two years.
Was a resolution ever found to this problem? Can anyone update this thread?
(bugs in this area have been fixed in 7.6).
I suggest doing what is suggest on the site linked.
Note: The Code::Blocks team does NOT fix bugs in gdb.
If you want it fixed; I suggest finding the gdb produced by the MinGW team instead of a third party like TDM etc.
Reproduce the problem using the command line interface of gdb.
Submit the way to reproduce the bug.
I don't have any problem on the recobb's test code.
Every test case works fine.
I'm using PCX's MinGW GCC 4.6.3, and GDB CVS build myself.