Memory dump using Ping .net

Question

I'm trying to do a ping to a server in a Windows Forms Application but when my program is running, I have memory dump on my computer. Very, very strange.

In my method I only have:

private void CheckServer()
{
    this.txResponse.Text = "";

    IPAddress IpAdress = IPAddress.Parse("anAdress");
    Ping ping = new Ping();

    PingReply pingToReply = ping.Send(IpAdress);

    if (pingToReply.Status == IPStatus.Success)
        txResponse.Text = pingToReply.Status.ToString();
}

I really don't understand what is going on. I'm using Visual Studio 2012 with .NET Framework 4.5 on Windows 8.If it is necessary more information, please let me know.

Answer 1

Verify that the parsing of the IP Address is successful; otherwise check the surrounding processing outside of the CheckServer method.

Answer 2

Ahhh, the joys of programming having a program blow up when there is absolutely nothing wrong with the code... (your code looks fine other than putting a try/catch block around it)

It could be a hardware issue (memory, disk etc), bad dll, or any number of things that go bump in the night. I assume you have tried rebooting your computer, and pinging your server at the DOS prompt. If not do so.

One thing you could try is to call ping.exe directly with a command line/ip of your choice synchronously or asynchronously, see http://www.codeproject.com/Articles/25983/How-to-Execute-a-Command-in-C and then parse the output to get what you need (lines starting with "Reply from" or "Request timed out." or even the % loss line.

Another thing to try is bypass the c# Ping and PingReply calls entirely and use net sockets and a timer, see http://sourceforge.net/projects/pingutil/?source=typ_redirect particularly the ping.cs file.

These solutions would allow you to potentially write around the problem, but it does not necessarily solve the problem at hand, which does not appear to programming related from the code you have provided.

OK, other thoughts... 1)Do a rebuild all on your project 2) Try compiling using an older version of .NET 3) Create a new project and copy block the source into the newly created files. 4) run the project on another computer to see if you get the same results. Any exception error that may or may not be generated should never cause a core dump.

Yet another option is to analyze the core dump, for an application, see: http://sourceforge.net/projects/core-analyzer/ and also check out Tool for analyzing java core dump

Worse comes to worse, you may have to reload Visual Studio and/or .NET.