How is this stack trace possible in .Net?

As in the comments to your question, weird stack traces such as this arise when one or more stack traces are output right after one another.

As in the comments to your question, weird stack traces such as this arise when one or more stack traces are output right after one another: Log. WriteLine(Environment. StackTrace) try { SomethingThatThrowsAnException(); } catch (Exception e) { Log.

WriteLine(e. StackTrace); // better to do Log. WriteLine(e) to get the message }.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.