en Copyright 2015 Java http://172.16.0.5:8080/history/llvm-project-15.0.7/clang/test/Modules/Inputs/crash-recovery/Frameworks/module.modulemap#b3a0fa48 [ModuleMap][CrashReproducer] Collect headers from inner frameworks(1) Collect headers under inner frameworks (frameworks inside otherother frameworks).(2) Make sure we also collect the right header files inside them.More info on (2):Consider a dummy framework module B, with header Frameworks/B/B.h. Nowconsider that another framework A, with header Frameworks/A/A.h, has alayout with a inner framework Frameworks/A/Frameworks/B/B.h, where the"B/B.h" part is a symlink for Frameworks/B/B.h. Also assume thatFrameworks/A/A.h includes <B/B.h>.When parsing header Frameworks/A/A.h, framework module lookup isperformed in search for B, and it happens that"Frameworks/A/Frameworks/B/B.h" path is registered in the module insteadof real "Frameworks/B/B.h". This occurs because"Frameworks/A/Frameworks/B/B.h" is scanned first by the FileManager,when looking for inner framework modules under Frameworks/A/Frameworks.This makes Frameworks/A/Frameworks/B/B.h the default cached named insidethe FileManager for the B.h file UID.This leads to modules being built without consistent paths to underlyingheader files. This is usually not a problem in regular compilation flow,but it's an issue when running the crash reproducer. The issue is thatclangs collect "Frameworks/A/Frameworks/B/B.h" but not"Frameworks/B/B.h" into the VFS, leading to err_mmap_umbrella_clash. Somake sure we also collect the original header.Differential Revision: http://reviews.llvm.org/D20194rdar://problem/25880368llvm-svn: 269502 List of files: /llvm-project-15.0.7/clang/test/Modules/Inputs/crash-recovery/Frameworks/module.modulemap Fri, 13 May 2016 22:21:51 +0000 Bruno Cardoso Lopes <bruno.cardoso@gmail.com>