Geek Answers Handbook

Are .NET applications immune to classic pointer errors?

Is there any article or evidence that .NET applications are immune to low-level errors?

I am talking about classic pointer errors that we see in a C ++ application, memory overflow, problems with DEP , etc. on the.

I am talking about .NET applications that do not use "unsafe" code, from my experience in this case there can only be problems with memory leaks or classic coding errors (for example, stack overflow), but I have never seen low-level errors.

Can anyone comment on this?

+5
source share
6 answers

, .NET , ...

  • - - - - , , BCL , ...

    . , .

    . , , .NET.

, exec [data], .NET - ( ).

, , :

" # .NET CLR" ftp://ftp.inf.ethz.ch/pub/publications/diss/th17003.pdf

+4

, , , , , , , , , , Windows COM-.

+2

-, , , (, LDAP, , ), , "" , , , , ...
. .NET . , -, , , , , !
- , , , , , , - , , ++.
.NET , - , .NET. , . , , IDisposable, unsafe.

0

?

, , , . Pagefiles , , ( ).

-, .Net- , , , . .

0

- .NET. , , , GC . ,.NET , .

0

, :

  • ,
  • ,

, ++, , new delete. new delete, . , , , . (, ) . , , . , , - , .

, GC, . , . , " " . " " " ", , , ++. , , .

0

More articles:


All Articles