Re: pointers and Windows debugging

Greg Hudson wrote:

>On Mon, 2003-01-06 at 19:11, Philip Martin wrote:
>
>
>>John Barstow <John_Barstow@gfsg.co.nz> writes:
>>
>>
>>>1) Pointers are not initialized to NULL. This may not matter too much on
>>>Unix, but on Windows, uninitialized pointers point to random locations in
>>>memory. This makes debugging very painful and bugs very unpredictable -
>>>especially since the problem is less pronounced in debug mode.
>>>
>>>
>
>
>
>>Not sure why you say this affects Windows more than Unix.
>>
>>
>
>In Unix, an uninitialized pointer might, conceivably, scribble over
>memory owned by the current application. But it's much more likely to
>cause a bus error or segmentation fault. In Windows, as I understand
>the argument, an unintialized pointer might scribble over memory owned
>by another application, or by the OS.
>
What? "Excretum bovis", as the Romans used to say. Windows has quite as
much memory protection as Unix, at least for 32-bit apps.

-- 
Brane Čibej   <brane_at_xbc.nu>   http://www.xbc.nu/brane/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org