-
Ian Lance Taylor authored
These new methods help find the compilation unit to pass to the LineReader method in order to find the line information for a PC. The Ranges method also helps identify the specific function for a PC, needed to determine the function name. This uses the .debug.ranges section if necessary, and changes the object file format packages to pass in the section contents if available. Change-Id: I5ebc3d27faaf1a126ffb17a1e6027efdf64af836 Reviewed-on: https://go-review.googlesource.com/20769Reviewed-by:
Austin Clements <austin@google.com> Run-TryBot: Ian Lance Taylor <iant@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org>
d1b8871f
| Name |
Last commit
|
Last update |
|---|---|---|
| .. | ||
| cycle.c | ||
| cycle.elf | ||
| line-clang.elf | ||
| line-gcc.elf | ||
| line1.c | ||
| line1.h | ||
| line2.c | ||
| ranges.c | ||
| ranges.elf | ||
| split.c | ||
| split.elf | ||
| typedef.c | ||
| typedef.elf | ||
| typedef.elf4 | ||
| typedef.macho |