dolfin team mailing list archive

[Anders Logg <logg@xxxxxxxxx>]

On Tue, Mar 18, 2008 at 03:19:53PM +0100, Ilmar Wilbers wrote:
> 
> 
> johannr@xxxxxxxxx wrote:
> > On Tue, Mar 18, 2008 Dag Lindbo wrote:
> >   
> >>  > The enablePydolfin flag should be fixed now and if you don't have swig,
> >>  > PyDOLFIN will be disabled.
> >>
> >> It works. Thanks!
> >>
> >>  >
> >>  >> *) Builds with output even if
> >>  >>     BoolOption("enableDebug", "Build with debug information", 0)
> >>  >
> >>  > Are you perhaps talking about a enableVerbose option or something like
> >>  > that? This is currently not implemented and I'm not sure if there are
> >> any
> >>  > plans for it either. The enableDebug flag only adds additional debug
> >>  > information to the compiler. It seems to work fine on my system.
> >>
> >> Sorry.I'm getting more output than usual, on the following form:
> >> Debug: size = 1 [at dolfin/function/DiscreteFunction.cpp:215 in
> >> interpolate()]
> >>     
> >
> > Ok, I now see what you mean. Ilmar has confirmed the same behavior.
> >
> >   
> >> I assumed that this had to do with the dubug flag. How do I get the
> >> "normal" verbosity level?
> >>     
> >
> > It should be only to set enableDebug=0. I'm not sure way it doesn't work.
> > We need to dig deeper into this.
> >
> >   
> >> Also, where do I find a logfile from
> >> configuration? It would be nice to see what it found (and where).
> >>     
> >
> > There is a log file in scons/simula_scons.log but at the moment it is not
> > very useful.
> >
> > Johannes
> >
> >
> > _______________________________________________
> > DOLFIN-dev mailing list
> > DOLFIN-dev@xxxxxxxxxx
> > http://www.fenics.org/mailman/listinfo/dolfin-dev
> >   
> i have been digging a bit, and the -DDEBUG flag does what it is supposed 
> to, namely defining assertions. The message Dag is referring to, and 
> which I also get, is due to dolfin_debug1(...). As far as I can 
> understand from doc/manual/chapters/logsystem.tex, this is the correct 
> behaviour, as the default value is 0, meaning all debug messages will be 
> printed unless it is set at a higher level (see 
> bench/fem/passembly/main.cpp).
> 
> Anyone more familiar with the logging system care to shed some light 
> upon this issue?
> 
> ilmar

It would be very simple to remove all debug messages when not running
in debug mode. I'm not sure what the correct behavior is. Suggestions?

We would only need to do the same thing for dolfin_debug as we've done
for dolfin_assert (#ifdef DEBUG) in the file

  dolfin/log/log.h

-- 
Anders