Discussion:
Mechanism for this oddity?
(too old to reply)
Vincent Fatica
2009-10-23 02:08:27 UTC
Permalink
On XP SP3, I start WinWord (Office 07) and minimize it. Using ProcessExplorer
(SysInternals v 11.04) I "suspend" WinWord (I figure ProcessExplorer suspends
each thread of WinWord). Then I open an Explorer window and navigate to my
profile dir ... Favorites ... double-click on a link ... nothing happens,
Explorer's caption includes "not responding". If I try to close the Explorer
window, I'm prompted to terminate Explorer (cancel that). If I go back to
ProcessExplorer and "resume" WinWord, all's well; the link opens and Explorer's
OK.

While I don't think it's a good idea to suspend an app like that, I'm curious
about the mechanism by which this peculiar interaction takes place ... any
speculation?

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?
--
- Vince
Igor Tandetnik
2009-10-23 03:02:46 UTC
Permalink
Post by Vincent Fatica
On XP SP3, I start WinWord (Office 07) and minimize it. Using ProcessExplorer
(SysInternals v 11.04) I "suspend" WinWord (I figure ProcessExplorer suspends
each thread of WinWord). Then I open an Explorer window and navigate to my
profile dir ... Favorites ... double-click on a link ... nothing happens,
Explorer's caption includes "not responding". If I try to close the Explorer
window, I'm prompted to terminate Explorer (cancel that). If I go back to
ProcessExplorer and "resume" WinWord, all's well; the link opens and Explorer's
OK.
While I don't think it's a good idea to suspend an app like that, I'm curious
about the mechanism by which this peculiar interaction takes place ... any
speculation?
See SendMessage, read aboud DDE.
Post by Vincent Fatica
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.
--
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
Vincent Fatica
2009-10-23 04:24:58 UTC
Permalink
On Thu, 22 Oct 2009 23:02:46 -0400, "Igor Tandetnik" <***@mvps.org>
wrote:

|See SendMessage, read aboud DDE.

That makes some sense.

|> 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.
--
- Vince
Igor Tandetnik
2009-10-23 06:28:20 UTC
Permalink
Post by Vincent Fatica
Post by Igor Tandetnik
Post by Vincent Fatica
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
Vincent Fatica
2009-10-23 13:59:33 UTC
Permalink
On Fri, 23 Oct 2009 02:28:20 -0400, "Igor Tandetnik" <***@mvps.org>
wrote:

|Vincent Fatica wrote:
|> On Thu, 22 Oct 2009 23:02:46 -0400, "Igor Tandetnik" <***@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?

All I see is

00000005 00000004 00000001 ntdll!DbgBreakPoint
00000000 00000000 00000000 ntdll!DbgUiRemoteBreakin+0x2d
--
- Vince
Loading...