Recently, two users of our software from the same company began to experience random closures (without error messages, failure dialogs, closing dialogs, etc.). We were able to isolate what the two systems had along with specific software (Mobile Broadband Device Manager). When this software works, our software accidentally closes for ~ 2 minutes. If we exit the broadband manager, our software will work without restrictions.
I cannot think of any reasons why there would be any interaction between our software and them. Our network does not have access to software, and in any case, the broadband modem is not connected.
We have provided work to the customer (run our software as an administrator or exit the mobile broadband manager before launching our software), but we want to solve the problem so as not to worry about doing any of this.
I connected a remote debugger to our software, but I was not sure where to look for exactly how our software was dying. Debugging ends with exit code 0 when our process is complete.
My question is, how can I find out how / why the Win32 process is being killed and what can I do to prevent this from happening?
Edit: I opened the broadband manager and DLLs that it uses in a hex editor, and it references an executable file with the same name as ours. Therefore, I assume that the link. Renaming our executable eliminates the problem for our users, but unfortunately the Sprint SmartView is stupid.
Change To help a rare other developer: "If your executable is named phoenix.exe , and your end users run Sprint SmartView, then why does your program die accidentally. Renaming your executable will solve this (or spend several months trying to figure out your life who should tell Sprint to really allow this.) The file that mentions phoenix.exe specifically is WwanCoreSdk.dll .
c ++ windows process winapi kill
eco
source share