Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
RE: [cdt-dev] Long compiler error messages not readable in the Pr oblems view. 
man gcc has the following 

Options to Control Diagnostic Messages Formatting 

Traditionally, diagnostic messages have been formatted irrespective of
the output device's aspect (e.g. its width, ...). The options described
below can be used to control the diagnostic messages formatting
algorithm, e.g. how many characters per line, how often source location
information should be reported. Right now, only the C++ front end can
honor these options. However it is expected, in the near future, that
the remaining front ends would be able to digest them correctly. 
-fmessage-length=n
        Try to format error messages so that they fit on lines of about
        n characters. The default is 72 characters for g++ and 0 for the
        rest of the front ends supported by GCC. If n is zero, then no
        line-wrapping will be done; each error message will appear on a
        single line.
-fdiagnostics-show-location=once
        Only meaningful in line-wrapping mode. Instructs the diagnostic
        messages reporter to emit once source location information; that
        is, in case the message is too long to fit on a single physical
        line and has to be wrapped, the source location won't be emitted
        (as prefix) again, over and over, in subsequent continuation
        lines. This is the default behavior.
-fdiagnostics-show-location=every-line
        Only meaningful in line-wrapping mode. Instructs the diagnostic
        messages reporter to emit the same source location information
        (as prefix) for physical lines that result from the process of
        breaking a message which is too long to fit on a single line. 
        
        
On Thu, 2005-11-10 at 13:29 -0700, Kim Lux wrote:
> On Thu, 2005-11-10 at 14:18 -0500, Doug Schaefer wrote:
> > The best thing to do is to go back to the build console and look at it
> > there. 
> 
> The problem with that is on big builds the bug results are hard to find
> in the console text and further more the build text is larger than the
> console memory.  So they aren't even there to look at in some cases. 
> 
> > The Eclipse Problems view really wasn't built to deal with long
> > messages, especially multi-line messages that we've had problems with
> > in the past (and current, I guess as well).
> 
> I dunno what to say.  This problem almost makes eclipse un usable for
> us.  
> 
> In Project -> Properties->"C/C++ Make Project"-> "Make Builder", I have
> "Stop on first build error" checked off.  Why isn't it stopping ?
> 
> gcc always has long error printouts.  How are other people using gcc ?
> Is there a flag for "short error descriptions" that I should be using ?
>  
-- 
Kim Lux,  Diesel Research Inc.

Back to the top