Hi root people::
I have a very vexing rootcint problem and would appreciate suggestions
on how to fix it.
I maintain the GLAST Windows terminal server
(glast-ts.phys.washington.edu, W2K), which has been infected with a
peculiar rootcint disease. It just crashes! I've made exhaustive
comparisons between the environment for this machine and others for
which the identical code and our current ROOT installation (v3.04.02)
works fine. The crash [The instruction at "0x778734b" referenced memory
at "0x0000034". The memory could not be "read"] occurs after rootcint
has processed all 17 input files, leaving an output that compiles ok,
but does not define expected functions.
Looking at the files created by rootcint, I have a clue: the "good"
generated source file starts like this:
//
// File generated by c:\extlib/ROOT\v3.04.02\root\bin\rootcint at Wed
Apr 16 11:44:36 2003.
// Do NOT change. Changes will be lost next time file is generated
//
#include "RConfig.h"
#if !defined(R__ACCESS_IN_SYMBOL)
//Break the privacy of classes -- Disabled for the moment
#define private public
#define protected public
#endif
#include "reconRootData_rootcint.h"
[...]
While a "bad" source file is quite different:
/********************************************************
* reconRootData_rootcint.cxx
********************************************************/
#include "reconRootData_rootcint.h"
#ifdef G__MEMTEST
#undef malloc
#undef free
#endif
[...]
Does this mean anything to someone? Thanks in advance.
--Toby Burnett
University of Washington
This archive was generated by hypermail 2b29 : Thu Jan 01 2004 - 17:50:11 MET