[petsc-dev] making BuildSystem hard to debug

[Matthew Knepley]

On Wed, Mar 21, 2012 at 10:24 AM, Barry Smith <bsmith at mcs.anl.gov> wrote:

>
> On Mar 21, 2012, at 8:38 AM, Matthew Knepley wrote:
>
> > On Wed, Mar 21, 2012 at 8:22 AM, Barry Smith <bsmith at mcs.anl.gov> wrote:
> >
> >  Matt,
> >
> >   One thing that has always pissed me off about BuildSystem but for some
> reason I never had the energy to bitch about is when a compile goes wrong,
> BuildSystem logs the source code that wouldn't compiler BUT IT DOES NOT LOG
> THE CONTENTS OF THE TWO FILES
> >
> > #include "confdefs.h"
> > #include "conffix.h"
> >
> > MAKING DEBUGGING HARDER. Can you please have BuildSystem log these files
> when it logs the source code that didn't compiler.
> >
> > We originally did this. It was way too long. I just debugged the same
> thing.
>
>   If you just dump it on a crash then length doesn't matter.  Without it
> one is left to completely guess exactly what is in them and could have
> triggered the problem.
>

The compile routine does not decide whether to crash, so I had configure.py
dump these headers if there was an exception. I
can test it later today.

  Matt


>   Barry
>
> >
> >    Matt
> >
> >   Thanks
> >
> >
> >   Barry
> >
> >
> >
> >
> >
> > --
> > What most experimenters take for granted before they begin their
> experiments is infinitely more interesting than any results to which their
> experiments lead.
> > -- Norbert Wiener
>
>


-- 
What most experimenters take for granted before they begin their
experiments is infinitely more interesting than any results to which their
experiments lead.
-- Norbert Wiener
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20120321/17af18ad/attachment.html>