diff options
| author | hunt <hunt> | 2006-10-12 18:20:29 +0000 |
|---|---|---|
| committer | hunt <hunt> | 2006-10-12 18:20:29 +0000 |
| commit | 5e3bb38362cf477a75c33bf9c3b31a03faa1bf17 (patch) | |
| tree | 04942b939f9881eca760b928786014cca20e9bd7 /runtime/stack.c | |
| parent | fabf5ed4db3cce35725023ebc424ffe28a7dd74a (diff) | |
| download | systemtap-steved-5e3bb38362cf477a75c33bf9c3b31a03faa1bf17.tar.gz systemtap-steved-5e3bb38362cf477a75c33bf9c3b31a03faa1bf17.tar.xz systemtap-steved-5e3bb38362cf477a75c33bf9c3b31a03faa1bf17.zip | |
Fix comment.
Diffstat (limited to 'runtime/stack.c')
| -rw-r--r-- | runtime/stack.c | 6 |
1 files changed, 0 insertions, 6 deletions
diff --git a/runtime/stack.c b/runtime/stack.c index dbbac9ac..a52dbfee 100644 --- a/runtime/stack.c +++ b/runtime/stack.c @@ -18,12 +18,6 @@ */ /** @addtogroup stack Stack Tracing Functions - * Without frames the best that can be done here is to scan the stack and - * display everything that fits in the range of a valid IP. Things like function pointers - * on the stack will certainly result in bogus addresses in the backtrace. - * - * With debug info, we could get a proper backtrace, but it would be too slow to do - * during a probe. We can eventually make this a postprocessing feature. * * @{ */ |