Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cdt-dev] Possible Bug in org.eclipse.cdt.managedbuilder.internal.buildmodel.BuildDescription
Still, the bug does not tell how tell how we can reproduce.

Thanks,
Andrew


On Mon, Jun 24, 2013 at 11:50 AM, Marc-André Laperle <marc-andre.laperle@xxxxxxxxxxxx> wrote:
Hi Joseph,

I think this was already reported:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=408525

If you push a patch to gerrit it's more likely to get looked at and accepted.

http://wiki.eclipse.org/Getting_started_with_CDT_development
http://wiki.eclipse.org/CDT/git#Using_Gerrit_for_CDT

Marc-Andre

From: cdt-dev-bounces@xxxxxxxxxxx [cdt-dev-bounces@xxxxxxxxxxx] on behalf of Joseph Henry [Joseph.Henry@xxxxxxx]
Sent: Monday, 24 June 2013 11:29 AM
To: cdt-dev@xxxxxxxxxxx
Subject: [cdt-dev] Possible Bug in org.eclipse.cdt.managedbuilder.internal.buildmodel.BuildDescription

Hi,

 

I am on a team at my company to integrate our development build process into the Eclipse CDT.

 

I think I might have ran across a bug in the CDT code.

 

I am using the latest Juno version of the plugin.

 

In the class org.eclipse.cdt.managedbuilder.internal.buildmodel.BuildDescription beginning at line 1005:

 

if(projLocation.isPrefixOf(outProjPath)) {

        // absolute location really points to same place the project lives, so it IS a project file

        outProjPath = outProjPath.removeFirstSegments(projLocation.segmentCount());

        outFullPath = projLocation.append(outProjPath.removeFirstSegments(projLocation.segmentCount()));

        outWorkspacePath = fProject.getFullPath().append(outProjPath);

}

 

This is the area of code that is causing me problems. It seems like the first line after the if should not be there, or if it is, then the “outProjPath.removeFirstSegments(projLocation.segmentCount())” should not be in the second line.

 

This causes the first two path segments after the project location to be lost, which causes a resource conflict in a certain situation.

 

 

Here is an example that will cause the resource conflict.

 

INPUT FILE -------------- OUTPUT FILE

C:\Project\subdir1\src\file1.c ------------------- C:\Project\subdir1\out\dir2\file1.obj

C:\Project\subdir2\src\file1.c ------------------- C:\Project\subdir2\out\dir2\file1.obj

 

As you can see, these files have the same name, and produce output of the same name, but the path is unique, so a resource conflict should not exist, But given the above code, the variable outFullPath will be transformed to C:\Project\dir2\file1.obj instead of C:\Project\subdir2\out\dir2\file1.obj which is what I am expecting.

 

 

How can I go about getting this patched in my release?

 

Thanks,

Joseph Henry.

 

 


_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev


Back to the top