query: How to find, from which include file a C preprocessor definition was taken?
positive_passages.docid: 25365
positive_passages.text: How to know (in GCC) when given macro/preprocessor symbol gets declared?
negative_passages.docid: 23706
negative_passages.text: How to detect reliably Mac OS X, iOS, Linux, Windows in C preprocessor?
negative_passages.docid: 136301
negative_passages.text: Reading a C file, read an extra line, why?
negative_passages.docid: 45099
negative_passages.text: What is the most convenient way to read definitions of in-memory symbols when we don't have the source files? (Spelunking tools)
negative_passages.docid: 107911
negative_passages.text: How should I detect unnecessary #include files in a large C++ project?
negative_passages.docid: 19987
negative_passages.text: Where are static variables stored in C and C++?
negative_passages.docid: 138188
negative_passages.text: Separate "include" and "src" folders for application-level code?
negative_passages.docid: 63761
negative_passages.text: Finding all .cpp and .h files and moving them to ~/junk
negative_passages.docid: 31742
negative_passages.text: Tentative definitions in C and linking
negative_passages.docid: 54869
negative_passages.text: Preprocessor directive in C# for importing based on platform
negative_passages.docid: 96756
negative_passages.text: Is it a good practice to place C++ definitions in header files?
negative_passages.docid: 43582
negative_passages.text: source code of c/c++ functions
negative_passages.docid: 19130
negative_passages.text: How do you get assembler output from C/C++ source in gcc?
negative_passages.docid: 138122
negative_passages.text: Organization of C files
negative_passages.docid: 77884
negative_passages.text: Which parts of an ELF executable get loaded into memory, and where?
negative_passages.docid: 106132
negative_passages.text: How to compile .c file with OpenSSL includes?
negative_passages.docid: 19993
negative_passages.text: C preprocessor # and ## operators