summaryrefslogtreecommitdiffstats
path: root/tapsets.cxx
diff options
context:
space:
mode:
authorfche <fche>2006-04-08 17:42:33 +0000
committerfche <fche>2006-04-08 17:42:33 +0000
commit34ca7d84b495e97a756cb09db579ff9997af4fda (patch)
tree8a2d1892b1a8ae444da392fac7ed6b43945bf9ad /tapsets.cxx
parentdc2230237753ab23520ce1d842b20cce52c763be (diff)
downloadsystemtap-steved-34ca7d84b495e97a756cb09db579ff9997af4fda.tar.gz
systemtap-steved-34ca7d84b495e97a756cb09db579ff9997af4fda.tar.xz
systemtap-steved-34ca7d84b495e97a756cb09db579ff9997af4fda.zip
* comment tweaks
Diffstat (limited to 'tapsets.cxx')
-rw-r--r--tapsets.cxx14
1 files changed, 4 insertions, 10 deletions
diff --git a/tapsets.cxx b/tapsets.cxx
index 5ed40080..55221347 100644
--- a/tapsets.cxx
+++ b/tapsets.cxx
@@ -892,16 +892,10 @@ dwflpp
void resolve_prologue_endings (map<Dwarf_Addr, func_info> & funcs)
{
// This heuristic attempts to pick the first address that has a
- // source line distinct from the function declaration's (entrypc's).
- // This should be the first statement *past* the prologue.
- //
- // However, for some tail-call optimized functions
- // ("sys_exit_group" in linux 2.6), there might be only a single
- // line record for the function. We guess at this situation if
- // the "next" line record refers to an address past the
- // dwarf_highpc of the current function. In this case, we back
- // down to the address from the previous line record.
- //
+ // source line distinct from the function declaration's. In a
+ // perfect world, this would be the first statement *past* the
+ // prologue.
+
assert(module);
assert(cu);