<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div></div><div><br><div><div>On Jun 14, 2013, at 18:44 , Utkarsh Ayachit wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div dir="ltr">Michael,<div><br></div><div>Any plugin that you build externally need to be "fixed" so it they doesn't refer to the libraries it was built with. </div><div><br></div><div style="">Try the following:</div>
<div style=""><br></div><div style="">> otool -L <plugin>.dylib</div><div style=""><br></div><div style="">What does the output show?</div><div style="">It will show paths to the libraries that the plugin was built against.</div>
<div style=""><br></div><div style="">Now do the same for a plugin under the /Applications/ParaVeiw.app/ e.g.</div><div style="">> otool -L /Applications/ParaView.app/Contents/Plugins/libEyeDomeLightingView.dylib</div><div style="">
<br></div><div style="">Look at the result. This library refers to dependencies using @executable_path/.../ unlike your plugin (I assume).</div><div style=""><br></div><div style="">You need to "fixup" your plugin dylib to refer to correct libraries. That can be done using install_name for each of the incorrectly referenced libraries.</div>
<div style=""><br></div><div style="">> install_name_tool -change <old name> <new name> <plugin>.dylib</div><div style=""><br></div><div style="">You can generally write a python or shell script to do the same.</div>
<div style=""><br></div><div style="">e.g. to get a list of libraries that the plugin refers to using non-relative paths, you can do the following:</div><div style=""><br></div><div style="">> otool -l <YOURPLUGIN>.dylib | grep " name" | sort | uniq | sed "s/name\ //" | grep -v "@" | sed "s/ (offset.*)//"</div>
<div style=""><br></div><div style="">Any of those names that refer to your ParaView build directory need to be fixed. So you can extend the query to remove any paths not in your build directory ....and so on.</div><div style=""><br>
</div><div style="">Utkarsh</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, Jun 14, 2013 at 8:19 AM, Michael Schlottke <span dir="ltr"><<a href="mailto:m.schlottke@aia.rwth-aachen.de" target="_blank">m.schlottke@aia.rwth-aachen.de</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word">Hi everyone,<div><br></div><div>I tried the new RC3 and I still get the same errors when trying to load a self-compiled plugin from the paraview.app application:</div>
<div><br></div><div>##############################################</div><div><div>objc[59843]: Class vtkCocoaTimer is implemented in both /Applications/ParaView 4.0.0-RC3.app/Contents/MacOS/../Libraries/libvtkRenderingOpenGL-pv4.0.1.dylib and /Users/mic/.BuiltFromSource/.builds/ParaView-4.0.0-RC3/lib/libvtkRenderingOpenGL-pv4.0.1.dylib. One of the two will be used. Which one is undefined.</div>
<div>objc[59843]: Class vtkCocoaServer is implemented in both /Applications/ParaView 4.0.0-RC3.app/Contents/MacOS/../Libraries/libvtkRenderingOpenGL-pv4.0.1.dylib and /Users/mic/.BuiltFromSource/.builds/ParaView-4.0.0-RC3/lib/libvtkRenderingOpenGL-pv4.0.1.dylib. One of the two will be used. Which one is undefined.</div>
<div>objc[59843]: Class vtkCocoaFullScreenWindow is implemented in both /Applications/ParaView 4.0.0-RC3.app/Contents/MacOS/../Libraries/libvtkRenderingOpenGL-pv4.0.1.dylib and /Users/mic/.BuiltFromSource/.builds/ParaView-4.0.0-RC3/lib/libvtkRenderingOpenGL-pv4.0.1.dylib. One of the two will be used. Which one is undefined.</div>
<div>objc[59843]: Class vtkCocoaGLView is implemented in both /Applications/ParaView 4.0.0-RC3.app/Contents/MacOS/../Libraries/libvtkRenderingOpenGL-pv4.0.1.dylib and /Users/mic/.BuiltFromSource/.builds/ParaView-4.0.0-RC3/lib/libvtkRenderingOpenGL-pv4.0.1.dylib. One of the two will be used. Which one is undefined.</div>
<div>libprotobuf ERROR /Users/mic/.BuiltFromSource/.sources/ParaView-4.0.0-RC3-source/ThirdParty/protobuf/vtkprotobuf/src/google/protobuf/descriptor_database.cc:109] Symbol name "google.protobuf.NamePart" conflicts with the existing symbol "google.protobuf.NamePart".</div>
<div>libprotobuf FATAL /Users/mic/.BuiltFromSource/.sources/ParaView-4.0.0-RC3-source/ThirdParty/protobuf/vtkprotobuf/src/google/protobuf/descriptor.cc:860] CHECK failed: generated_database_->Add(encoded_file_descriptor, size):</div>
<div>Abort trap: 6</div><div>##############################################</div><div><br></div><div>It seems to be that the problem is related to the fact that I compile the plugin using <b>ParaView_DIR= /Users/mic/.BuiltFromSource/.builds/ParaView-4.0.0-RC3</b>. However, the bundled paraview.app (in my case: /Applications/ParaView 4.0.0-RC3.app) brings its own libraries (which generally smart, I guess, since that way the builddir can be deleted after doing 'make install'). Unfortunately, I have not been able to build my plugins against the /Applications/ParaView 4.0.0-RC3.app (cmake doesn't find ParaView there).</div>
<div><br></div><div>I see three possible ways to solve this problem: </div><div><br></div><div>1) Modify the paraview.app bundle so that it is recognized as a valid paraview dir (and probably copy some more files there that are needed for the plugins)</div>
<div>2) Modify the paraview.app bundle so that it does NOT have it's own library files anymore, but resorts to using the ones in the builder</div><div>3) Modify the plugin loading mechanism so that it does not reload libraries that were already loaded in ParaView</div>
<div><br></div><div>However, here I run out of ideas and knowledge of how to achieve this. Does anyone have a hot fix or even a permanent solution to this issue?</div><div><br></div><div>Regards,</div><div><br></div><div>
Michael</div><div><div class="h5"><div><br></div><div><div>On May 30, 2013, at 17:27 , Utkarsh Ayachit wrote:</div><br><blockquote type="cite"><div>Michael,<br><br>I'll try to figure out the install issue. In the mean time, if you're<br>
intrested in creating redistrubtable app bundles, refer to<br><a href="http://paraview.org/Wiki/ParaView/Superbuild" target="_blank">http://paraview.org/Wiki/ParaView/Superbuild</a><br><br>Utkarsh<br><br>On Thu, May 30, 2013 at 9:20 AM, Michael Schlottke<br>
<<a href="mailto:m.schlottke@aia.rwth-aachen.de" target="_blank">m.schlottke@aia.rwth-aachen.de</a>> wrote:<br><blockquote type="cite">Hi Utkarsh,<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">
Thanks for the URL. After checking all relevant entries, we still found no possible for the cause of the bug, so back to square one. We then instrumented the plugin code heavily with debug statements, and finally found an answer to our problem: as it turned out, there was a minor bug in the plugin code (related to the ordering of points) that for some reason never materialized when running the plugin with ParaView 3.14, but which caused some serious trouble in 4.0.0. After fixing the bug, the plugin now runs happily with 4.0.0-RC2 and on OS X!<br>
</blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Thanks again for your help! It would be great if the "make install" issue could be resolved (if I can help, let me know), since right now I have no way to start ParaView from the OS X gui (I need to go into a terminal and manually execute paraview from there). Creating a symlink to the paraview.app in <builddir>/bin/paraview.app won't work, and neither does copying the paraview.app folder manually.<br>
</blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Regards,<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Michael<br></blockquote><blockquote type="cite"><br></blockquote>
<blockquote type="cite">On May 29, 2013, at 23:22 , Utkarsh Ayachit wrote:<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><blockquote type="cite">Michael,<br></blockquote></blockquote><blockquote type="cite">
<blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">In theory, "make install" should work. OsX can be pretty unforgiving<br></blockquote></blockquote><blockquote type="cite">
<blockquote type="cite">with library paths. I'll try to see if I can reproduce the issue and<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">track it down.<br></blockquote></blockquote><blockquote type="cite">
<blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">As for the segfault, it's hard to say without looking at the code.<br></blockquote></blockquote><blockquote type="cite">
<blockquote type="cite">There have been quite a few changes since VTK 6.0. Refer to this:<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><a href="http://www.vtk.org/Wiki/VTK/VTK_6_Migration_Guide" target="_blank">http://www.vtk.org/Wiki/VTK/VTK_6_Migration_Guide</a><br>
</blockquote></blockquote><blockquote type="cite"><blockquote type="cite">Hopefully that helps.<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite">
<blockquote type="cite">Utkarsh<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite">
<blockquote type="cite">On Wed, May 29, 2013 at 10:10 AM, Michael Schlottke<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><<a href="mailto:m.schlottke@aia.rwth-aachen.de" target="_blank">m.schlottke@aia.rwth-aachen.de</a>> wrote:<br>
</blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">Hi Utkarsh,<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">
<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">(a) is the location of the paraview.app bundle that is created when building ParaView on OS X and running "make install"<br>
</blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">(b) is the original build directory<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">
<blockquote type="cite"><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">If I go to the build directory and run "./bin/paraview.app/Contents/MacOS/paraview", it actually works, so thank you very much! How come that the "installed" version has problems with duplicate symbols, while the original one doesn't? This seems to render the "make install" command rather useless on OS X…(or maybe its a feature and I just fail to see the purpose).<br>
</blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">
However, now that the plugin loads correctly, if I try to load a dataset with the reader, ParaView crashes with a segfault: "Segmentation fault: 11"<br></blockquote></blockquote></blockquote><blockquote type="cite">
<blockquote type="cite"><blockquote type="cite">From my plugin's debug output I know that the "RequestData" function returns without problems, but after that there's no more output until the segfault. The exact same plugin works without problems on a Linux machine. The only explanation that I can come up with is that there was a (silent) change from 3.14 to 4.00 that does not manifest in the plugin itself but only later in the pipeline. Can you make anything of this?<br>
</blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">
Thanks a lot in advance!<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">
<blockquote type="cite">Michael<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">
<blockquote type="cite">On May 29, 2013, at 15:37 , Utkarsh Ayachit wrote:<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote>
<blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">Looks like you have two builds of ParaView:<br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">
<blockquote type="cite"><blockquote type="cite">(a) /Applications/ParaView 4.0.0-RC2.app/<br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">
(b) / /Users/mic/.BuiltFromSource/.builds/ParaView-4.0.0-RC2/<br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote>
</blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">Which one (a) or (b) was the plugin built against and which one are<br></blockquote></blockquote>
</blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">you trying to load it in?<br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite">
<blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">
Utkarsh<br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite">
<blockquote type="cite"><blockquote type="cite"><blockquote type="cite">On Wed, May 29, 2013 at 8:58 AM, Michael Schlottke<br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">
<blockquote type="cite"><blockquote type="cite"><<a href="mailto:m.schlottke@aia.rwth-aachen.de" target="_blank">m.schlottke@aia.rwth-aachen.de</a>> wrote:<br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite">
<blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">Hi,<br></blockquote></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">
<blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">
We have created a custom reader plugin for our simulation data. On Linux<br></blockquote></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">
<blockquote type="cite">using ParaView 3.14 the plugin works without problems. However, we have not<br></blockquote></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">
<blockquote type="cite"><blockquote type="cite">succeeded to get the plugin to work on Mac OS X:<br></blockquote></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">
<blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">
When trying to load the plugin in the Plugin Manager, ParaView crashes and<br></blockquote></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">
<blockquote type="cite">leaves the following message on the command line:<br></blockquote></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">
<blockquote type="cite"><br></blockquote></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">objc[54821]: Class vtkCocoaTimer is implemented in both<br>
</blockquote></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">/Applications/ParaView<br></blockquote>
</blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">4.0.0-RC2.app/Contents/MacOS/./../Libraries/libvtkRenderingOpenGL-pv4.0.1.dylib<br>
</blockquote></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">and<br></blockquote></blockquote></blockquote>
</blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">/Users/mic/.BuiltFromSource/.builds/ParaView-4.0.0-RC2/lib/libvtkRenderingOpenGL-pv4.0.1.dylib.<br>
</blockquote></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">One of the two will be used. Which one is undefined.<br>
</blockquote></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">objc[54821]: Class vtkCocoaServer is implemented in both<br>
</blockquote></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">/Applications/ParaView<br></blockquote>
</blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">4.0.0-RC2.app/Contents/MacOS/./../Libraries/libvtkRenderingOpenGL-pv4.0.1.dylib<br>
</blockquote></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">and<br></blockquote></blockquote></blockquote>
</blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">/Users/mic/.BuiltFromSource/.builds/ParaView-4.0.0-RC2/lib/libvtkRenderingOpenGL-pv4.0.1.dylib.<br>
</blockquote></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">One of the two will be used. Which one is undefined.<br>
</blockquote></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">objc[54821]: Class vtkCocoaFullScreenWindow is implemented in both<br>
</blockquote></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">/Applications/ParaView<br></blockquote>
</blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">4.0.0-RC2.app/Contents/MacOS/./../Libraries/libvtkRenderingOpenGL-pv4.0.1.dylib<br>
</blockquote></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">and<br></blockquote></blockquote></blockquote>
</blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">/Users/mic/.BuiltFromSource/.builds/ParaView-4.0.0-RC2/lib/libvtkRenderingOpenGL-pv4.0.1.dylib.<br>
</blockquote></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">One of the two will be used. Which one is undefined.<br>
</blockquote></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">objc[54821]: Class vtkCocoaGLView is implemented in both<br>
</blockquote></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">/Applications/ParaView<br></blockquote>
</blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">4.0.0-RC2.app/Contents/MacOS/./../Libraries/libvtkRenderingOpenGL-pv4.0.1.dylib<br>
</blockquote></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">and<br></blockquote></blockquote></blockquote>
</blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">/Users/mic/.BuiltFromSource/.builds/ParaView-4.0.0-RC2/lib/libvtkRenderingOpenGL-pv4.0.1.dylib.<br>
</blockquote></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">One of the two will be used. Which one is undefined.<br>
</blockquote></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">libprotobuf ERROR<br></blockquote></blockquote>
</blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">/Users/mic/.BuiltFromSource/.sources/ParaView-4.0.0-RC2/ThirdParty/protobuf/vtkprotobuf/src/google/protobuf/descriptor_database.cc:109]<br>
</blockquote></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">Symbol name "google.protobuf.NamePart" conflicts with the existing symbol<br>
</blockquote></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">"google.protobuf.NamePart".<br>
</blockquote></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">libprotobuf FATAL<br></blockquote></blockquote>
</blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">/Users/mic/.BuiltFromSource/.sources/ParaView-4.0.0-RC2/ThirdParty/protobuf/vtkprotobuf/src/google/protobuf/descriptor.cc:860]<br>
</blockquote></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">CHECK failed: generated_database_->Add(encoded_file_descriptor, size):<br>
</blockquote></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">Abort trap: 6<br></blockquote></blockquote>
</blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote></blockquote></blockquote>
<blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">The used OS X version is 10.7.5, with ParaView 4.0.0-RC2. Compilation was<br></blockquote></blockquote>
</blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">done (both plugin and ParaView itself) with clang 3.1.<br></blockquote>
</blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote></blockquote>
</blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">Since I wouldn't even know where to start searching for the cause of this<br></blockquote>
</blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">problem, any help or input is appreciated.<br></blockquote>
</blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote></blockquote>
</blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">Regards,<br></blockquote></blockquote></blockquote></blockquote></blockquote><blockquote type="cite">
<blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">
<blockquote type="cite"><blockquote type="cite">Michael<br></blockquote></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">
<br></blockquote></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote>
</blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">--<br></blockquote></blockquote></blockquote></blockquote></blockquote><blockquote type="cite">
<blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">Michael Schlottke<br></blockquote></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">
<blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">
<blockquote type="cite">SimLab Highly Scalable Fluids & Solids Engineering<br></blockquote></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">
<blockquote type="cite">Jülich Aachen Research Alliance (JARA-HPC)<br></blockquote></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">
<blockquote type="cite">RWTH Aachen University<br></blockquote></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">
Wüllnerstraße 5a<br></blockquote></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">52062 Aachen<br>
</blockquote></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">Germany<br></blockquote></blockquote>
</blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote></blockquote></blockquote>
<blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">Phone: <a href="tel:%2B49%20%28241%29%2080%2095188" value="+492418095188" target="_blank">+49 (241) 80 95188</a><br>
</blockquote></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">Fax: <a href="tel:%2B49%20%28241%29%2080%2092257" value="+492418092257" target="_blank">+49 (241) 80 92257</a><br>
</blockquote></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">Mail: <a href="mailto:m.schlottke@aia.rwth-aachen.de" target="_blank">m.schlottke@aia.rwth-aachen.de</a><br>
</blockquote></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">Web: <a href="http://www.jara.org/jara-hpc" target="_blank">http://www.jara.org/jara-hpc</a><br>
</blockquote></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote>
</blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote></blockquote></blockquote><blockquote type="cite">
<blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">_______________________________________________<br></blockquote></blockquote></blockquote></blockquote></blockquote><blockquote type="cite">
<blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">Paraview-developers mailing list<br></blockquote></blockquote></blockquote></blockquote></blockquote><blockquote type="cite">
<blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><a href="mailto:Paraview-developers@paraview.org" target="_blank">Paraview-developers@paraview.org</a><br></blockquote></blockquote>
</blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><a href="http://public.kitware.com/mailman/listinfo/paraview-developers" target="_blank">http://public.kitware.com/mailman/listinfo/paraview-developers</a><br>
</blockquote></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote>
</blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote><blockquote type="cite"><br></blockquote></div></blockquote></div><br></div></div>
</div></div></blockquote></div><br></div>
</blockquote></div><br></div></body></html>