Your debugger will tell you exactly where the problem was. This suggests to me that you might be accessing an array with a negative index or something like that, or otherwise using an out-of-bounds index in some other array.Īnother possibility is that you accessed an object that has been deleted.Īnd yet another possibility is that you have reinterpreted (cast) an object to something that it is not and wound up with an address through a bogus calculation. And 228 bytes sounds suspiciously like the size of a modest-sized class or object. Now that could be the base address of some dll (unlikely) or it couldīe a memory mapped file or device of some kind (more likely to get a round number this way than through the heap). It's only 228 bytes before that big round number.
On the other hand, the 0x02fffdd8 bit looks suspiciously like it is just before a big round number address of 0x03000000. Your address is pretty close to where the heap would put a big memory block of
The address 0x02fffdd8 is most likely just past the end of a heap block or just before a large mapped buffer.įor example, if I allocate memory with malloc and I allocate 0x1000000 bytes (sixteen million bytes) then I might get an address like 0x01c90040 (ending at 0x02c9003F). It happens when you access (read or write) an address that is not mapped to any physical memory or is protected (tried to write to read-only memory, for example). And it is very likely code you wrote that is causing the problem (as opposed to you using a 3rd party library incorrectly or something like that.)ĠxC0000005 is the code for an access violation. So this suggests that there is some code in your PcsPrintSrvc500.exe project that But let me put on my psychic helmet and see whatĪlmost all C++ exe programs are loaded at 0x00400000, and your exception is at 0x0040161b, which means that it is only about 0x161b bytes into your main module code.
I strongly suggest you ask questions in this forum by providing a bit of background and much more detail. (And you haven't given nearly enough information to determine exactly why it happened. Did you write PcsPrintSrvc500.exe? You have a bug.
0 kommentar(er)
