[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
[Cdt-launch-inbox] [Bug 217292] Starter.exe behaving different than Runtime.exec() during building Standard Make Project
|
https://bugs.eclipse.org/bugs/show_bug.cgi?id=217292
Product/Component: CDT / cdt-launch
Johann Draschwandtner <johann.draschwandtner@xxxxxxxxxxxxx> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |johann.draschwandtner@windri
| |ver.com
--- Comment #3 from Johann Draschwandtner <johann.draschwandtner@xxxxxxxxxxxxx> 2008-02-06 06:30:39 -0400 ---
I've encountered similar problems which were related to a fast (dual core)
machine on windows.
The problematic steps were that in
Java_org_eclipse_cdt_utils_spawner_Spawner_exec0 a thread for watching the
process termination was started. It seemed that this thread couldn't get the
correct handle for the process to wait for. Therefore it terminated and for the
spawner treated this as if the process couldn't be started.
The patch I attached uses the no thread for the startup check, e.g. it waits
either for the waitEvent, which is triggered from starter.exe and indicates
that everything went ok, or for the process termination which indicates that
the starter.exe wasn't run correctly.
2nd part of the thread was to do the proper cleanup, which is still handled by
the thread, but it's only launched if everything started up correcly. When
passing the args to the thread procedure I noticed that some memory might get
screwed up, so I explicitely handled this.
--
Configure bugmail: https://bugs.eclipse.org/bugs/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
