Le lundi 19 décembre 2011 à 00:23 +0100, Jean-Marc Desperrier a écrit :
> On 16/12/2011 19:01, Christian Dywan wrote:
> > [...]
> > So meanwhile we're running with these settings and 16GB RAM:
> > [...]
> > And yet the tables are incomplete, half the tables are missing. Syntax
> > highlighting works but there's no type information in the HTML.
> > [...]
> > I do wonder what other magic values should be required, or if there is
> > something missing with how mozilla-central needs to be compiled - did
> > you use any special options? I don't see a problem in the DXR setup, and
> > memory is not the bottleneck.
> 
> I have compared the result of the sample requests on dxr.lanedo and 
> dxr.mozilla, and found something interesting in the "nsAccessible::" one.
> 
> Initially the results look similar, but after a while the lanedo 
> instance starts outputing an enormous chunk that comes from 
> obj-x86_64-unknown-linux-gnu/toolkit/library/libxul.so, and many others 
> follow from various binary files, like 
> /obj-x86_64-unknown-linux-gnu/accessible/src/base/nsAccUtils.o , etc.
> There's nothing like that in the result from the mozilla instance.
> 
> It seems the binary outputs of the compilation got included by error in 
> the list of the file that must be indexed, and this might be the cause 
> for the problems you are meeting. Maybe you need to make sure the 
> obj-x86_64-unknown-linux-gnu directory is created outside of the path 
> that is indexed.

You were right, we have that folder in mozilla-central/. Two questions:

1) Can I safely remove the whole obj-x86_64-unknown-linux-gnu folder ?
2) Can you confirm that this is configured by running:
source /opt/dxr/source/dxr/setup-env.sh $SRC_DIR $BUILD_DIR ?

Thanks, 

Lionel

_______________________________________________
dev-static-analysis mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-static-analysis

Reply via email to