Posted by Fox on 2000-05-27
This problem is bringing out some old memories of similiar, "unsolvable" bugs
I've had in the past. Each of them had two things in common: 1) they were dang
annoying, and unsolvable-looking 2) the cause and solution were so simple that I
beat myself up for not realizing it!
Complex problems, 99% of the time, have simple solutions.
Anyway...if you'll send me the code, I'll be happy to look at it, and try some
things on my own. Be mindful, I'm using a Microsoft Visual C++ 6.0 compiler. I
hope compatability won't be an issue.
I want to help you; I can't think of the times I've had similiar problems and
there was no one there to help me!
Send me a zip file containing everything needed to compile and run the
program. I'll be happy to look at it myself, if you're willing to let me, that is.
I just feel that I should offer my help.
/*
> Every time I'm more coonfused with this error.
>
> I just ran the program with gdb and found that the kernel32.dll page fault
> isn't produced by my code rather than by DefWindowProc when it handles the
> WM_NCCREATE message(I think).
> Another thing is that the value of the lParam parameter changes every time
> that gdb runs, but the error "Cannot access memory at address 0x2000000." is
> always the same.
>
> I even try to compile it on VC5 but it gives me almost the same
> error("Unhandled exception in webcolor.exe(KERNEL32.DLL): 0xC00000fd: Stack
> Overflow") and freeze the machine.
>
> I try to move the code to another message(WM_RBUTTONDOWN) and it works just
> as is supossed to do. Then, if the error only shows up when I move it to the
> WM_COMMAND message handler what could it be the error?.
/*
Remember, complex problems almost
always have simple solutions!
Previous post | Next post | Timeline | Home