Re: I am loosing the handle

it sounds like you have a buffer overrun occuring somewhere in your code.
if you are using visual studio, you can set a breakpoint on the memory
address of the handle and see who is overwriting the value.

there is no part of memory that is protected at run time. you have a bug,
you need to fix it. even thoug the hComm field is now staying the same,
some other part of the class is now being overwritten where hComm used to
be.

d

--
Please do not send e-mail directly to this alias. this alias is for
newsgroup purposes only.
This posting is provided "AS IS" with no warranties, and confers no rights.


"Neil" <neil@xxxxxxxxxx> wrote in message
news:XIDpf.6483$k76.1399@xxxxxxxxxxxxxxxxxxxxxxxxx
>
> "Alexander Grigoriev" <alegr@xxxxxxxxxxxxx> wrote in message
> news:OG9oEmLBGHA.272@xxxxxxxxxxxxxxxxxxxxxxx
>> Access specifiers are compile-time protection. They don't affect run
>> time.
>>
>
> Then, I guess by moving hComm from the top, to a bottom place is what
> actually did it? Because now it is not getting overwritten, what could
> have
> caused this to happen? How can I protect hComm from getting overwritten
> in
> the future? Is there a part in memory that is protected during run-time?
>
> Thank you,
> Neil
>
>


.

Relevant Pages

  • Re: [Lit.] Buffer overruns
    ... or are you talking about the pagein memory instead? ... but no additional memory protection ... Fiddling the storage keys for page protection could interfer ... since with virtual address space architecture fetch protection can be ...
    (sci.crypt)
  • Re: [Lit.] Buffer overruns
    ... > 360/67 had added virtual memory and features like segment sharing to ... > Fiddling the storage keys for page protection could interfer ...
    (sci.crypt)
  • Re: For the AdaOS folks
    ... > about how the structure of AmigaOS relates to microkernels ... > AmigaOS didn't have any protection and divided everything ... But the libraries weren't like those ... supports memory protection. ...
    (comp.lang.ada)
  • Re: Protect one single byte on Linux/x86 / sharing libraries / process mem. layout
    ... I did some research on the topic "memory protection" using google, ... PDE and PTE leave some space for managment information, ... The MMU generates a exception ...
    (comp.os.linux.development.system)
  • Linux Memory / Process Management on x86
    ... As you might have guessed from the topic "Linux Memory / Process ... I did some research on the topic "memory protection" using google, ... translated to a linear address by "ignoring" everything above bit 31. ... PDE and PTE leave some space for managment information, ...
    (comp.os.linux.misc)