Re: Mechanism for this oddity?

From:

"Igor Tandetnik" <itandetnik@mvps.org>

Newsgroups:

microsoft.public.vc.language

Date:

Fri, 23 Oct 2009 02:28:20 -0400

Message-ID:

<O8aaJo6UKHA.220@TK2MSFTNGP02.phx.gbl>

Vincent Fatica wrote:

On Thu, 22 Oct 2009 23:02:46 -0400, "Igor Tandetnik" =

<itandetnik@mvps.org>

wrote:

In a another related incident, if I try (in WinDBg) to start a =

certain 3rd-party

GUI app while WinWord is so suspended, WinDbg tells me "debugee is =

running"

right in the middle of loading DLLs. Resuming WinWord causes this =

app to resume

loading DLLs, with UXTheme.dll being the first one loaded after the =

hang. Only

then does the app actually appear. ... any speculation?

See SendMessage. For whatever reason, the app is broadcasting a =

message.

I doubt the app has gotten to any code that the author wrote. It just =

sits

there ("debugee is running") right in the middle of loading system =

DLLs.

Loading DLLs means running code in DllMain.

If you are curious, why don't you break at this point and see what's on =
the call stack?
--
With best wishes,
Igor Tandetnik

With sufficient thrust, pigs fly just fine. However, this is not =
necessarily a good idea. It is hard to be sure where they are going to =
land, and it could be dangerous sitting under them as they fly overhead. =
-- RFC 1925