Stop 0xC2 or BAD_POOL_CALLER
Hi,
I got a small problem. A customer of mine has had the following crash.
Stop 0xC2 or BAD_POOL_CALLER
0x00000040 Starting address Start of system address space This value is always zero Attempt to free usermode address to kernel pool
I found the area of the problem, but I have some questions about stl.
in one of our communication classes we use:
vector<string> masAcceptedIdentificationResponses;
constructor:
NIGPIB::NIGPIB(const int vnBoard, const int vnPrim, const int vnSec) : masAcceptedIdentificationResponses(0)
I think the problem is caused in one "driver" we create the object dynamically and with the other we inherate this class.
Can someone tell if I am right or totally wrong?
I do not mind being wrong, but I have been looking at this code for about 8 hours and I am starting to run out of options.
any points would be great,
Jewe
Re: Stop 0xC2 or BAD_POOL_CALLER
Mabe you should try to recreate the "crash" in small scale.
Write a small program to do that and then ask your question again.
Re: Stop 0xC2 or BAD_POOL_CALLER
Dude,
If I could recreate the problem then I would be the luckiest man on the planet. the thing is that I can not reproduce it.. :(
Re: Stop 0xC2 or BAD_POOL_CALLER
Re: Stop 0xC2 or BAD_POOL_CALLER
Solution to this problem was installing the latest GPIB drivers