Can string concatenation be corrupted or confusing with insecure C # code?

Question

If I manage the C # managed string in place (for example, canceled its characters) using pointers in a block or unsafe method, can this unsafe implementation confuse or ruin .NET pool pooling mechanisms?

The proposed managed string is created in managed code and passed to an unsafe method that needs to be manipulated.

An example of this scenario:

 static void Main(string[] args) { string s = "this is a test"; UnsafeReverse(s); Console.WriteLine(s); // displays "tset a si siht" // assume more managed strings are created and used along with the affected s. } static unsafe void UnsafeReverse(string str) { int len = str.Length; fixed (char* pStr = str) { char* p1 = pStr; char* p2 = pStr + len - 1; char tmp; while (p1 < p2) { tmp = *p1; *p1 = *p2; *p2 = tmp; ++p1; --p2; } } } 

Answer 1

Sure. Just write this to see the damage:

  static readonly string DontMessWithStrings = "this is a test"; static void Main(string[] args) { string s = "this is a test"; UnsafeReverse(s); Console.WriteLine(DontMessWithStrings); } 

[Edit by OP] The result of the DontMessWithStrings display is "tset a si siht" , although this variable is never directly affected by the string manipulation code!