Xeon
Brought to you by:
grzegok
Menu
▾
▴
We're using version 3.5.
The behaviour is this: the launcher executable starts up but will not "fork and exec" to the javaw.exe.
The process when inspected doesn't have any DLLs. And, it cannot be killed from the taskmgr.exe. It's necessary to reboot.
I'll have a go with 3.7 and let you know.
Hello, I'm not aware of any problems of MinGW running on Xeon processors. Is that a virtual machine? Please run the program with --l4j-debug option to create a log file, perhaps then I'll be able to figure out something more.
Grzegorz
Hello Grzegorz, thanks for help. launch4j executables will not launch correctly on this machine. We get a new kind of zombie process. Process Explorer states that it has no DLLs loaded. And the process can't be killed using the taskmgr.
He's a remote user, so we haven't got access to his machine and are unable to reproduce it.
We want to move him to a new host configuration.
Do you know of any tools that would allow us to trace the loading process?
I see. Unfortunately I don't know any such tool. Perhaps the problem is a quite old version of MinGW, although this is the first bug report of this kind. I'm attaching version 3.6.1 of launch4j which was compiled with a newer version of gcc. You can try it out to see if it helps, but don't use it for distributing your software. It will produce false positive virus warnings on some machines, and I've dropped this version and returned to the old gcc/MinGW.