public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "dilyan.palauzov at aegee dot org" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug compile/17972] New: Double #include Date: Fri, 13 Feb 2015 15:58:00 -0000 [thread overview] Message-ID: <bug-17972-4717@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=17972 Bug ID: 17972 Summary: Double #include Product: gdb Version: HEAD Status: NEW Severity: normal Priority: P2 Component: compile Assignee: unassigned at sourceware dot org Reporter: dilyan.palauzov at aegee dot org deheader -v (git://gitorious.org/deheader/deheader.git) reported, that in the gdb tree some .c files #include more than once the same .h file: m32r-tdep.c has more than one inclusion of "objfiles.h" mi/mi-main.c has more than one inclusion of "inferior.h" python/py-block.c has more than one inclusion of "symtab.h" stubs/ia64vms-stub.c has more than one inclusion of <ssdef.h> testsuite/gdb.threads/create-fail.c has more than one inclusion of <assert.h> testsuite/gdb.threads/create-fail.c has more than one inclusion of <stdio.h> testsuite/gdb.threads/fork-thread-pending.c has more than one inclusion of <unistd.h> testsuite/gdb.threads/watchpoint-fork-mt.c has more than one inclusion of <unistd.h> tui/tui-source.c has more than one inclusion of "symtab.h" These delay unncessary the compilation. -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2015-02-13 15:51 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-02-13 15:58 dilyan.palauzov at aegee dot org [this message] 2015-02-13 17:05 ` [Bug compile/17972] " xdje42 at gmail dot com
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-17972-4717@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=gdb-prs@sourceware.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).