From: "fche at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug translator/28244] New: linux objtool imposes symbol length limits on generated function names
Date: Wed, 18 Aug 2021 16:33:51 +0000 [thread overview]
Message-ID: <bug-28244-6586@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=28244
Bug ID: 28244
Summary: linux objtool imposes symbol length limits on
generated function names
Product: systemtap
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: translator
Assignee: systemtap at sourceware dot org
Reporter: fche at redhat dot com
Target Milestone: ---
Some function/symbol names generated for probes/functions encode stap
tapset/source file name paths. These can get long, but that's not usually a
problem. However, linux objtool (in recent kernels) is invoked during the
kbuild process, and it imposes a 128-char limit. It looks like we have no
choice but to shorten these symbol names.
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2021-08-18 16:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-18 16:33 fche at redhat dot com [this message]
2021-08-20 16:24 ` [Bug translator/28244] " scox at redhat dot com
2021-08-30 16:44 ` fche at redhat 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-28244-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).