reason for dead lock, dead looping?

本文探讨了使用标准 Windows API 进程间通信时遇到的问题,特别是关于 WaitForInputIdle 的局限性和死锁现象。作者在尝试操作子进程窗口时遇到了未预期的行为,并详细记录了导致死锁的情况。

It seems not everything can be solved by normal windows api.

Like WaitForInputIdle(), even it works well.  Like while()-slee() insead. There is still a problem there.

After I got the handle to window class of the new child process's thread's window.

When I move the child process 's window, it can cause dead-lock with some unclear reason.

Because I don't know the routine of the child process window's initiation.

The parent process operating on SetWindowLong(m_hWndChild, ... ) caused the child gui program into dead-lock state

in some sistuations, not always.

I should really hijack api.


评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值