OpenE2K
/
binutils-gdb
12
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

* symtab.c (find_pc_sect_line): Revert change of 2001-11-13; add 

comment explaining that hand-written assembly code can have line
number info but no debug info for an enclosing function.
This commit is contained in:
Jim Blandy 2001-11-27 00:03:22 +00:00
parent b82eaaea7a
commit b77b1eb785
2 changed files with 12 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
gdb/ChangeLog
View File

@ -1,3 +1,9 @@
2001-11-26 Jim Blandy <jimb@redhat.com>
* symtab.c (find_pc_sect_line): Revert change of 2001-11-13; add
comment explaining that hand-written assembly code can have line
number info but no debug info for an enclosing function.
2001-11-26 Jakub Jelinek <jakub@redhat.com> 2001-11-26 Jakub Jelinek <jakub@redhat.com>
* sparc-nat.c (fetch_inferior_registers): Don't rely * sparc-nat.c (fetch_inferior_registers): Don't rely

13
gdb/symtab.c
View File

@ -1570,13 +1570,12 @@ find_pc_sect_line (CORE_ADDR pc, struct sec *section, int notcurrent)
INIT_SAL (&val); /* initialize to zeroes */ INIT_SAL (&val); /* initialize to zeroes */
/* Don't even think about line numbers if we can't find a function /* It's tempting to assume that, if we can't find debugging info for
symbol for PC. */ any function enclosing PC, that we shouldn't search for line
if (find_pc_function (pc) == NULL) number info, either. However, GAS can emit line number info for
{ assembly files --- very helpful when debugging hand-written
val.pc = pc; assembly code. In such a case, we'd have no debug info for the
return val; function, but we would have line info. */
}
if (notcurrent) if (notcurrent)
pc -= 1; pc -= 1;