public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
* [Bug debug/67163] New: g2 generates incorrect decl_line @ 2015-08-09 6:04 dehao at gcc dot gnu.org 2015-08-09 6:18 ` [Bug debug/67163] " dehao at gcc dot gnu.org ` (2 more replies) 0 siblings, 3 replies; 4+ messages in thread From: dehao at gcc dot gnu.org @ 2015-08-09 6:04 UTC (permalink / raw) To: gcc-bugs https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67163 Bug ID: 67163 Summary: g2 generates incorrect decl_line Product: gcc Version: 6.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: debug Assignee: unassigned at gcc dot gnu.org Reporter: dehao at gcc dot gnu.org Target Milestone: --- #g++ -c -o ValueStore.o -O2 -g1 ValueStore.ii #objdump --dwarf=info ValueStore.o|grep -A 2 isDuplicateOf <615> DW_AT_name : (indirect string, offset: 0x490): isDuplicateOf <619> DW_AT_decl_file : 11 <61a> DW_AT_decl_line : 297 #g++ -c -o ValueStore.o -O2 -g2 ValueStore.ii #objdump --dwarf=info ValueStore.o|grep -A 2 isDuplicateOf <5114> DW_AT_name : (indirect string, offset: 0x563d): isDuplicateOf <5118> DW_AT_decl_file : 51 <5119> DW_AT_decl_line : 150 g1 generates correct decl_line, but g2 generates incorrect decl_line (150 is the decl_line for another function: addValue) ^ permalink raw reply [flat|nested] 4+ messages in thread
* [Bug debug/67163] g2 generates incorrect decl_line 2015-08-09 6:04 [Bug debug/67163] New: g2 generates incorrect decl_line dehao at gcc dot gnu.org @ 2015-08-09 6:18 ` dehao at gcc dot gnu.org 2015-08-09 6:20 ` dehao at gcc dot gnu.org 2015-08-09 14:50 ` dehao at gcc dot gnu.org 2 siblings, 0 replies; 4+ messages in thread From: dehao at gcc dot gnu.org @ 2015-08-09 6:18 UTC (permalink / raw) To: gcc-bugs https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67163 --- Comment #1 from dehao at gcc dot gnu.org --- Created attachment 36157 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=36157&action=edit preprocessed file ^ permalink raw reply [flat|nested] 4+ messages in thread
* [Bug debug/67163] g2 generates incorrect decl_line 2015-08-09 6:04 [Bug debug/67163] New: g2 generates incorrect decl_line dehao at gcc dot gnu.org 2015-08-09 6:18 ` [Bug debug/67163] " dehao at gcc dot gnu.org @ 2015-08-09 6:20 ` dehao at gcc dot gnu.org 2015-08-09 14:50 ` dehao at gcc dot gnu.org 2 siblings, 0 replies; 4+ messages in thread From: dehao at gcc dot gnu.org @ 2015-08-09 6:20 UTC (permalink / raw) To: gcc-bugs https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67163 --- Comment #2 from dehao at gcc dot gnu.org --- Created attachment 36158 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=36158&action=edit preprocessed file ^ permalink raw reply [flat|nested] 4+ messages in thread
* [Bug debug/67163] g2 generates incorrect decl_line 2015-08-09 6:04 [Bug debug/67163] New: g2 generates incorrect decl_line dehao at gcc dot gnu.org 2015-08-09 6:18 ` [Bug debug/67163] " dehao at gcc dot gnu.org 2015-08-09 6:20 ` dehao at gcc dot gnu.org @ 2015-08-09 14:50 ` dehao at gcc dot gnu.org 2 siblings, 0 replies; 4+ messages in thread From: dehao at gcc dot gnu.org @ 2015-08-09 14:50 UTC (permalink / raw) To: gcc-bugs https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67163 --- Comment #4 from dehao at gcc dot gnu.org --- Right, in -g2 binary debug info, the decl_file is pointing to the header file in which the function is declared. However, if the definition is available, it makes more sense to point decl_file and decl_line where it's actually defined, right? Additionally, it's better to keep g1 and g2 debug info consistent. ^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2015-08-09 14:50 UTC | newest] Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2015-08-09 6:04 [Bug debug/67163] New: g2 generates incorrect decl_line dehao at gcc dot gnu.org 2015-08-09 6:18 ` [Bug debug/67163] " dehao at gcc dot gnu.org 2015-08-09 6:20 ` dehao at gcc dot gnu.org 2015-08-09 14:50 ` dehao at gcc dot gnu.org
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).