From: "fche at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug translator/31496] New: support DW_OP_bra (conditional branches) in dwarf location lists
Date: Fri, 15 Mar 2024 20:04:08 +0000 [thread overview]
Message-ID: <bug-31496-6586@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=31496
Bug ID: 31496
Summary: support DW_OP_bra (conditional branches) in dwarf
location lists
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: ---
stap should support location lists such as:
<8><1257ae4>: Abbrev Number: 15 (DW_TAG_call_site_parameter)
<1257ae5> DW_AT_location : 1 byte block: 54 (DW_OP_reg4 (rsi))
<1257ae7> DW_AT_call_value : 22 byte block: 9 ff 30 7d 0 8 20 24 30 29
28 1 0 16 13 b 60 fb 1a 23 c0 1b (DW_OP_const1s: -1; DW_OP_lit0; DW_OP_breg13
(r13): 0; DW_OP_const1u: 32; DW_OP_shl; DW_OP_lit0; DW_OP_eq; DW_OP_bra: 1;
DW_OP_swap; DW_OP_drop; DW_OP_const2s: -1184; DW_OP_and; DW_OP_plus_uconst:
3520)
(found in the fedora 38 6.4.15 kernel)
00449 case DW_OP_bra:
00450 // ??? Could copy the stack, recurse, and place both
00451 // traces in arms of a ternary_expression. No point
00452 // in doing that if this is never used, however.
00453 DIE ("conditional branches not supported");
00454 break;
https://issues.redhat.com/browse/RHEL-13009
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2024-03-15 20:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-15 20:04 fche at redhat dot com [this message]
2024-04-23 18:17 ` [Bug translator/31496] " amerey 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-31496-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).