On May 29, 2006, at 1:17 PM, Jack Howarth wrote:
In building xplor-nih against the gcc trunk, I noticed that there
is a c++ related
regression
I'll let Andrew comment if it sounds like anything he's seen. I'd
recommend a binary search to narrow down the translation unit and the
compiler version that went bad if the prospects of actually trying to
debug this are daunting.
Off-hand, sounds like throw across dylib/bundle boundary problem, or
someone using the wrong visibility on classes.
You can check for the later by something like:
nm -m *.o | c++filt | grep info | grep -v external
and seeing if you get any hits. If so, they could be the cause of
the problem.
The first case might be easier to test in the small, as if it is
totally busted, even the most trivial of programs will show the
breakage.
