From: "agentzh at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug runtime/26673] New: The kernel backtrace dumper should not use stack array which may lead to compilation errors
Date: Mon, 28 Sep 2020 19:36:55 +0000 [thread overview]
Message-ID: <bug-26673-6586@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=26673
Bug ID: 26673
Summary: The kernel backtrace dumper should not use stack array
which may lead to compilation errors
Product: systemtap
Version: unspecified
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: runtime
Assignee: systemtap at sourceware dot org
Reporter: agentzh at gmail dot com
Target Milestone: ---
Consider the following example when using a MAXBACKTRACE macro value larger
than 60 and the kernel backtrace dumper in the stap runtime, it will lead to
compilation errors due to the on-stack array "entries" in the function of the
stap runt
```
$ /opt/stap/bin/stap -DMAXBACKTRACE=61 -e 'probe begin { print_backtrace() }'
In file included from
/tmp/stapy7pTmc/stap_ec9093ee0dc3ecaa0481bbf9075a06bf_1049_src.c:79:
/opt/stap/share/systemtap/runtime/stack.c: In function
‘_stp_stack_print_fallback.isra.33.constprop’:
/opt/stap/share/systemtap/runtime/stack.c:235:1: error: the frame size of 520
bytes is larger than 512 bytes [-Werror=frame-larger-than=]
}
^
cc1: all warnings being treated as errors
make[1]: *** [scripts/Makefile.build:276:
/tmp/stapy7pTmc/stap_ec9093ee0dc3ecaa0481bbf9075a06bf_1049_src.o] Error 1
make: *** [Makefile:1581: _module_/tmp/stapy7pTmc] Error 2
WARNING: kbuild exited with status: 2
Pass 4: compilation failed. [man error::pass4]
```
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2020-09-28 19:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-28 19:36 agentzh at gmail dot com [this message]
2020-09-28 20:59 ` [Bug runtime/26673] " agentzh at gmail dot com
2020-09-28 21:13 ` agentzh at gmail dot com
2020-09-28 21:13 ` agentzh at gmail dot com
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-26673-6586@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=systemtap@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).