[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Bug gprofng/29700] New: [display collect] Issue a warning if callstack
From: |
ruud.vanderpas at oracle dot com |
Subject: |
[Bug gprofng/29700] New: [display collect] Issue a warning if callstack frames are no longer captured |
Date: |
Wed, 19 Oct 2022 13:02:55 +0000 |
https://sourceware.org/bugzilla/show_bug.cgi?id=29700
Bug ID: 29700
Summary: [display collect] Issue a warning if callstack frames
are no longer captured
Product: binutils
Version: 2.39
Status: NEW
Severity: enhancement
Priority: P2
Component: gprofng
Assignee: vladimir.mezentsev at oracle dot com
Reporter: ruud.vanderpas at oracle dot com
Target Milestone: ---
The data collection engine uses a buffer to store the call stack data. Once the
buffer is full, callstack frames are no longer captured. The default limit is
256 both for C/C++ and Java.
If frames have been dropped, this is shown in the output from "gprofng display
text" (<Truncated-stack>), but it will be helpful to also print a diagnostic
run-time message in case this has occurred.
This message should also explain how to increase the buffer size by changing
the value through environment variables GPROFNG_MAX_CALL_STACK_DEPTH (C/C++) or
GPROFNG_JAVA_MAX_CALL_STACK_DEPTH (Java).
The complication is that this warning should not be sent to stdout/stderr
per-se, or the user needs to have a way to disable these, because perhaps this
behaviour is known and desired.
This is why it might be better to include such a warning in a log file. An
added benefit is that other tools (e.g. display html) may pick this up.
--
You are receiving this mail because:
You are on the CC list for the bug.
- [Bug gprofng/29700] New: [display collect] Issue a warning if callstack frames are no longer captured,
ruud.vanderpas at oracle dot com <=