Project Home
Project Home		 Trackers
Trackers		 Documents
Documents		 Wiki
Wiki		 Discussion Forums
Discussions		 Project Information
Project Info
IDE/Discussion/General/Comipler Errors in dialog boxes/List of Posts
Forum Topic - Comipler Errors in dialog boxes: (11 Items)
   
Update
Kevin Stallard(deleted)
05/15/2009 1:54 PM
post29555
Comipler Errors in dialog boxes   
I would like to make a recomendation for the CDT.  When building, cleaning or doing other build related tasks, if there 
are errors, a dialog is presented to the user with the error information.

Besides the fact that the information is usually not all that helpful (i.e. "There are Errors" or some angle bracket 
wasn't properly terminated with another, etc ), it is incredibly anoying to have to wait for the outline to slide up and
 over from the bottom right of the screen to the middle and then have to dismiss it with either the ESC or the button on
 the dialog.

I would like to recommend that maybe a new view could be created that could contain a log of these errors, so instead of
 displaying them in a dialog box, a new entry could be netered in the log and read when desired.

Anyway, just my $.01 worth...

Kevin
Elena Laskavaia
05/15/2009 2:46 PM
post29563
Re: Comipler Errors in dialog boxes   
It should not be any dialog. What version you are using?

Kevin Stallard wrote:
> I would like to make a recomendation for the CDT.  When building, cleaning or doing other build related tasks, if 
there are errors, a dialog is presented to the user with the error information.
> 
> Besides the fact that the information is usually not all that helpful (i.e. "There are Errors" or some angle bracket 
wasn't properly terminated with another, etc ), it is incredibly anoying to have to wait for the outline to slide up and
 over from the bottom right of the screen to the middle and then have to dismiss it with either the ESC or the button on
 the dialog.
> 
> I would like to recommend that maybe a new view could be created that could contain a log of these errors, so instead 
of displaying them in a dialog box, a new entry could be netered in the log and read when desired.
> 
> Anyway, just my $.01 worth...
> 
> Kevin
> 
> _______________________________________________
> General
> http://community.qnx.com/sf/go/post29555
>
Christian Damus(deleted)
05/15/2009 2:50 PM
post29564
Re: Comipler Errors in dialog boxes   
Hi, Kevin,

Are you using one of the experimental builds from the IDE 4.6 stream?
There was an interval where compile errors would produce this dialog,
but that has since been remedied.  Errors are shown in the Problems view
and also in the C Build console.

Cheers,

Christian


On Fri, 2009-05-15 at 13:54 -0400, Kevin Stallard wrote:

> I would like to make a recomendation for the CDT.  When building, cleaning or doing other build related tasks, if 
there are errors, a dialog is presented to the user with the error information.
> 
> Besides the fact that the information is usually not all that helpful (i.e. "There are Errors" or some angle bracket 
wasn't properly terminated with another, etc ), it is incredibly anoying to have to wait for the outline to slide up and
 over from the bottom right of the screen to the middle and then have to dismiss it with either the ESC or the button on
 the dialog.
> 
> I would like to recommend that maybe a new view could be created that could contain a log of these errors, so instead 
of displaying them in a dialog box, a new entry could be netered in the log and read when desired.
> 
> Anyway, just my $.01 worth...
> 
> Kevin
> 
> _______________________________________________
> General
> http://community.qnx.com/sf/go/post29555
> 


________________________________________________________________________

Christian W. Damus
Software Developer, IDE Team
QNX Software Systems
Kevin Stallard(deleted)
05/15/2009 3:33 PM
post29576
Re: Comipler Errors in dialog boxes   
Thanks for your responses, I think I may have been a bit misleading.

It isn't that a compile error will be put into a dialog, but rather, if the managed build system or some non-gcc 
produced error occurs during the build process, then a dialog is presented.

It did it a little today, but seems to have calmed down.  Next time I get a sample, I'll post it.

Thanks
Kevin
Kevin Stallard(deleted)
05/15/2009 8:44 PM
post29595
Re: Comipler Errors in dialog boxes   
Found and example. Sometimes this appears and sometimes it doesn't, I guess it all depends how the stars are aligned 
when I start the IDE.

Anyway, this dialog sometimes appears when I clean a project.

Kevin
Attachment: Image BuildErrorDialog.jpg 39.23 KB
Christian Damus(deleted)
05/19/2009 12:40 PM
post29688
Re: Comipler Errors in dialog boxes   
Hi, Kevin,

This looks like a bug.  The builder should not be attempting to lock the
workspace when it is building a project.

Can you provide a reproducible scenario, steps to follow?  Perhaps your
workspace log file may have some entries before the error that can
provide clues.  This would seem to be precipitated by some other
unexpected condition, which should be logged.  Could you attach your
log?

Back to your original problem:  Eclipse-based tooling generally does
alert via dialog boxes when user-initiated actions fail to complete
normally.  Make errors are "normal" but failing to prepare to launch
make is not.  It may be that some configurability of problem reporting
is appropriate, or that the workbench is treating operations as user
tasks that it should not.  The workspace log of the error will help to
determine in which component we might look to address such concerns.

Cheers,

Christian

On Fri, 2009-05-15 at 20:44 -0400, Kevin Stallard wrote:

> Found and example. Sometimes this appears and sometimes it doesn't, I guess it all depends how the stars are aligned 
when I start the IDE.
> 
> Anyway, this dialog sometimes appears when I clean a project.
> 
> Kevin

-----8<-----
Kevin Stallard(deleted)
05/22/2009 11:33 PM
post29917
Re: Comipler Errors in dialog boxes   
Christian,

Thanks for the reply.  Attached is a log file.  Search for beginRule: R/ and you'll find one.

Thank you for looking into it.

Regards,
Kevin
Attachment: Text .log 948.41 KB
Christian Damus(deleted)
05/25/2009 10:10 AM
post29938
Re: Comipler Errors in dialog boxes   
Hi, Kevin,

Thanks for the log file.  It was illuminating.

The only way in which this particular problem can occur, is in projects
that are maintained in a source control system integrated with Eclipse's
Team framework.  I see from your log that the Perforce team provider is
failing to initialize in the context of some common CDT model management
operations.  Are the projects in which you get this build error managed
in Perforce?

If so, then it appears that the Perforce provider is requiring exclusive
access to the entire workspace in order to refresh a project, which in
the case of QNX-style projects, occurs on every build.  The build runs
in a context that locks only the individual project.

This is a condition for which the QNX project builder can check in
advance, so I shall raise an internal enhancement request for that
change.  Because our builder knows that it will require a refresh of the
project, it can check a priori the granularity of locking that will be
required in the workspace.

In the mean-time, I am unsure of how you can work around this problem
except by disconnecting your workspace projects from Perforce.  I am,
frankly, surprised that this problem is intermittent; it appears that it
should always occur.  Are there any particular actions that trigger the
error?  My best guess at this point is that Perforce can provide finer
granularity of locking if it is correctly initialized, but that
otherwise the Eclipse default of requiring a workspace-level lock kicks
in and causes your build failures.  Thus, the root cause would actually
be whatever is causing the CDT's internal model initialization to fail
in starting up the Perforce integration.

Cheers,

Christian
Kevin Stallard(deleted)
05/26/2009 4:09 AM
post29992
Re: Comipler Errors in dialog boxes   
Wow, thanks Christian,

I'll forward this on to Perforce.  Yes, we're using it.  They need to know about this.

Thanks again,
Kevin


> Hi, Kevin,
> 
> Thanks for the log file.  It was illuminating.
> 
> The only way in which this particular problem can occur, is in projects
> that are maintained in a source control system integrated with Eclipse's
> Team framework.  I see from your log that the Perforce team provider is
> failing to initialize in the context of some common CDT model management
> operations.  Are the projects in which you get this build error managed
> in Perforce?
> 
> If so, then it appears that the Perforce provider is requiring exclusive
> access to the entire workspace in order to refresh a project, which in
> the case of QNX-style projects, occurs on every build.  The build runs
> in a context that locks only the individual project.
> 
> This is a condition for which the QNX project builder can check in
> advance, so I shall raise an internal enhancement request for that
> change.  Because our builder knows that it will require a refresh of the
> project, it can check a priori the granularity of locking that will be
> required in the workspace.
> 
> In the mean-time, I am unsure of how you can work around this problem
> except by disconnecting your workspace projects from Perforce.  I am,
> frankly, surprised that this problem is intermittent; it appears that it
> should always occur.  Are there any particular actions that trigger the
> error?  My best guess at this point is that Perforce can provide finer
> granularity of locking if it is correctly initialized, but that
> otherwise the Eclipse default of requiring a workspace-level lock kicks
> in and causes your build failures.  Thus, the root cause would actually
> be whatever is causing the CDT's internal model initialization to fail
> in starting up the Perforce integration.
> 
> Cheers,
> 
> Christian
Christian Damus(deleted)
05/26/2009 10:02 AM
post30028
Re: Comipler Errors in dialog boxes   
Hi, Kevin,

As I mentioned, I suspect that the problem stems from the Perforce team
provider failing to initialize on the projects in which this problem is
manifest, which then results in the default pessimistic locking strategy
being applied by the Eclipse platform in lieu of the defunct Perforce
provider.  I would be extremely surprised if the Perforce provider,
itself, required a workspace-wide lock for refreshing a project under
its control:  they would have had many complaints about that before now.

So, the question is what in the interaction between the CDT model
initialization and the Perforce team provider is causing the provider
initialization to fail?  The log doesn't provide enough information.

Moreover, in your other reply, you mention that the error only occurs on
cleaning.  Does a re-build (not from clean) work and show  the results
that you expect?  Are there any projects for which clean consistently
works?  If so, how are they different?

Cheers,

Christian

On Tue, 2009-05-26 at 04:09 -0400, Kevin Stallard wrote:

> Wow, thanks Christian,
> 
> I'll forward this on to Perforce.  Yes, we're using it.  They need to know about this.
> 
> Thanks again,
> Kevin
> 

-----8<-----
Kevin Stallard(deleted)
05/26/2009 4:11 AM
post29993
Re: Comipler Errors in dialog boxes   
Hey Christian,

One other item, it only happens when I clean a project.

Best,
Kevin

Return


  A subsidiary of BlackBerry             All content ©2004-2013, QNX Software Systems