aboutsummaryrefslogtreecommitdiff
path: root/gdb/testsuite/gdb.python/py-section-script.py
diff options
context:
space:
mode:
authorJoel Brobecker <brobecker@gnat.com>2011-01-18 16:18:26 +0000
committerJoel Brobecker <brobecker@gnat.com>2011-01-18 16:18:26 +0000
commite3acb1155ba584a440ac0914d97e2884c9189324 (patch)
tree46158d8d763e3d5ceda88ad88d2d5aeee6693fef /gdb/testsuite/gdb.python/py-section-script.py
parent752573b2920d62193587f15cf8565b0e6bca416c (diff)
downloadbinutils-e3acb1155ba584a440ac0914d97e2884c9189324.zip
binutils-e3acb1155ba584a440ac0914d97e2884c9189324.tar.gz
binutils-e3acb1155ba584a440ac0914d97e2884c9189324.tar.bz2
[powerpc] breakpoint inserted past function end
On powerpc, the prologue scanner reads instruction after instruction, and just skips instructions that do not affect a frame. This means that it does not stop if if finds and unexpected instruction (which could possibly happen with optimization, I presume). To avoid scanning too many instructions, it tries to establish an upper limit. The upper limit is first computed using the debugging (line) info, but if that fails, it falls back on an arbitrary 100 bytes (or 25 instructions). The problem is that, if the function is shorter than those 25 instructions, we run the risk of skipping the entire function and returning a PC that's outside our function. In the event where we can find a symbol for a given PC (and therefore can determine function start and end addresses), but cannot find an upper limit using skip_prologue_using_sal, then we can at least limit make sure that the 25 instructions do not put us beyour our function. If it does, then further reduce the upper-limit to the end of the function. gdb/ChangeLog: * rs6000-tdep.c (rs6000_skip_prologue): Make sure that the prologue upper limit address is not greater than the function end address when the upper limit could not be computed using the debugging info.
Diffstat (limited to 'gdb/testsuite/gdb.python/py-section-script.py')
0 files changed, 0 insertions, 0 deletions