From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2206 invoked by alias); 26 Jan 2015 16:31:08 -0000 Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-prs-owner@sourceware.org Received: (qmail 1803 invoked by uid 55); 26 Jan 2015 16:30:31 -0000 From: "dtaylor at usendtaylorx2l dot lss.emc.com" To: gdb-prs@sourceware.org Subject: [Bug symtab/17866] incremental read missing header files Date: Mon, 26 Jan 2015 17:43:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: symtab X-Bugzilla-Version: 7.8 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: dtaylor at usendtaylorx2l dot lss.emc.com X-Bugzilla-Status: NEW X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2015-q1/txt/msg00129.txt.bz2 https://sourceware.org/bugzilla/show_bug.cgi?id=17866 --- Comment #2 from dtaylor at usendtaylorx2l dot lss.emc.com --- I have done some further investigation. First, most (all?) headers are known when using STABS. It is only an issue when using DWARF. With STABS, there are begin include and end include entries. And GDB notices them. The headers mentioned therein are known to GDB. With DWARF, at -g2 (the default), in the sample program I gave, there is no mention of the include file anywhere within the *.s file. Scanning the DWARF 4 document online I didn't find anyplace where it said that it had to record the header file names, though I was expecting it to record them so that a consumer would know the origins of structs, enum, and the like. In our experience, some headers are known but not most. I suspect that the known ones contain inline functions or something similar. At -g3 -- the value we use -- macro information is included. And since the information recorded includes the file and line where the macro is defined, the *.s file mentions the header files (n our build every *.h file has a header guard macro and therefore at least one macro). However, GDB does not seem to scan the .debug_macinfo section for file names on startup. I'm not familiar with the DWARF reader and haven't as yet got a clue as to how to modify GDB to change this behavior. -- You are receiving this mail because: You are on the CC list for the bug.