[Cdt-launch-inbox] [Bug 217292] New: Starter.exe behaving different than

[bugzilla-daemon@xxxxxxxxxxx]

https://bugs.eclipse.org/bugs/show_bug.cgi?id=217292  
Product/Component: CDT / cdt-launch
           Summary: Starter.exe behaving different than Runtime.exec()
                    during building Standard Make Project
           Product: CDT
           Version: 4.0.1
          Platform: PC
               URL: http://www.eclipse.org/newsportal/article.php?id=15360&g
                    roup=eclipse.tools.cdt#15360
        OS/Version: Windows XP
            Status: NEW
          Severity: major
          Priority: P3
         Component: cdt-launch
        AssignedTo: cdt-launch-inbox@xxxxxxxxxxx
        ReportedBy: marko.tomljenovic@xxxxxxxxxxxx


Build ID: 20070926042742

Steps To Reproduce:
I am (CDT is) calling a .cmd file that itself calls some other tools that
realize the software build (some parts are makefiles some are different
technology). If I build the project I get an error (Exec error:Launching
failed).

If I call the same command line through external tools the error is not
appearing. The difference between both mechanisms is that CDT uses the
starter.exe to run the command whereas the external tool calls it directly.

So I am asking myself now what does starter.exe do different ? 

Is there any documentation about the starter.exe? 

I found out something more regarding the failure. The failure during calling
the .cmd file (which itself calls an exe that determines and checks some PIDs)
is the result of a not expected/wrong/??? process id.


More information:
Win XP
If I fake the OS (debug session) to be Win98 the CDT CommonBuilder does not use
the Spawner class for command line execution but calls the command line
directly throug Runtime.exec(). In this faked case everything is working fine.


-- 
Configure bugmail: https://bugs.eclipse.org/bugs/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.