Strange hang with Dns.GetHostEntry

  • Thread starter Thread starter rob
  • Start date Start date
R

rob

I've seen an occasional hang on a call to Dns.GetHostEntry, but this
is tough to debug. The stack looks correct. The param is only
127.0.0.1, so it should not be difficult.

This is inconsistent (usually runs without a hitch). The odd thing is
that when I break, the exec point is right on Dns.GetHostEntry, but
hovering over the passed param yields a message: "Cannot evaluate
expression because a native frame is on top of the call stack"

This seems to correct itself Simply times out. I can then resume
exectution and things will go smoothly. But it will not time out
unless I break.

The errors that I've seen listed in conjunction with the "Cannot
evaluate" don't seem to relate to this.

Any insights?
 
I've seen an occasional hang on a call to Dns.GetHostEntry, but this
is tough to debug. The stack looks correct. The param is only
127.0.0.1, so it should not be difficult.

This is inconsistent (usually runs without a hitch). The odd thing is
that when I break, the exec point is right on Dns.GetHostEntry, but
hovering over the passed param yields a message: "Cannot evaluate
expression because a native frame is on top of the call stack"

This seems to correct itself Simply times out. I can then resume
exectution and things will go smoothly. But it will not time out
unless I break.

The errors that I've seen listed in conjunction with the "Cannot
evaluate" don't seem to relate to this.

Any insights?
Click to expand...

No ideas about this?
 
I've seen an occasional hang on a call to Dns.GetHostEntry, but this
is tough to debug. The stack looks correct. The param is only
127.0.0.1, so it should not be difficult.
[...]
Click to expand...

No ideas about this?
Click to expand...

Maybe if you posted your question to a newsgroup where questions about
network configuration issues are on-topic?

You're looking for a level of expertise that you have very poor odds of
finding here. The part of your problem where the timeout won't even occur
until you break in the debugger is certainly more C#/.NET-ish, but
fundamentally you seem to have more of a networking issue, not a
programming issue.

Pete
 
I've seen an occasional hang on a call to Dns.GetHostEntry, but this
is tough to debug. The stack looks correct. The param is only
127.0.0.1, so it should not be difficult.
[...]
Click to expand...

No ideas about this?
Click to expand...

Maybe if you posted your question to a newsgroup where questions about
network configuration issues are on-topic?

You're looking for a level of expertise that you have very poor odds of
finding here. The part of your problem where the timeout won't even occur
until you break in the debugger is certainly more C#/.NET-ish, but
fundamentally you seem to have more of a networking issue, not a
programming issue.

Pete
Click to expand...

No network programmers here? My news service has tons of programming
groups, but alas, nothing that deals with network programming under
C#. If you can suggest a relevant group, I will ask my news service
to add it.

The problem with this is that the Dns class is C#/.NET, so I doubt
that the Win32 or other groups will know what's going on with that
particular call. And it stalls on localhost (127.0.0.1), so it's not
even going out over the wire. Since it's intermittent, and often can
be stepped through by the debugger after breaking out of the hang,
there should be same way to resolve it, but damn if I can think of
anything.
 
Back
Top