public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "akhilesh.k at samsung dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug libc/30178] New: backtrace is not working on riscv
Date: Mon, 27 Feb 2023 13:46:44 +0000 [thread overview]
Message-ID: <bug-30178-131@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=30178
Bug ID: 30178
Summary: backtrace is not working on riscv
Product: glibc
Version: 2.36
Status: NEW
Severity: normal
Priority: P2
Component: libc
Assignee: unassigned at sourceware dot org
Reporter: akhilesh.k at samsung dot com
CC: drepper.fsp at gmail dot com
Target Milestone: ---
Hello
I am working on risk-v rv64imafdc-lp64d virtual environment, during glibc
testcases verification observed some of glibc functions are not working as per
expectation backtrack is one of them.
setup: gcc 12.2, glibc 2.33, binutils 2.39
Summary of test results:
201 FAIL
3907 PASS
62 UNSUPPORTED
18 XFAIL
backtrace Fail results
FAIL debug/tst-backtrace2
FAIL debug/tst-backtrace3
FAIL debug/tst-backtrace4
FAIL debug/tst-backtrace5
FAIL debug/tst-backtrace6
Even when sample test case "man backtrace" sample test case this always return
depth 1
$riscv64-unknown-linux-gnu-gcc -march=rv64g -o backtrace -rdynamic
backtrace.c
even checked with and without fp(-fno-omit-frame-pointer/--omit-frame-pointer)
$./backtrace 3
backtrace() returned 1 addresses
./backtrace(myfunc3+0x18) [0x10b58]
$uname -a
Linux buildroot 5.4.228 #1 SMP Wed Jan 18 13:15:58 IST 2023 riscv64 GNU/Linux
is this expected because for riscv I am able to find any separate backtrace
implementation in glibc/sysdeps like arm.
Also In glibc release note such fail case for riscv.
https://sourceware.org/glibc/wiki/Release/2.36
https://sourceware.org/glibc/wiki/Release/2.33
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2023-02-27 13:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-27 13:46 akhilesh.k at samsung dot com [this message]
2023-02-27 13:47 ` [Bug libc/30178] " akhilesh.k at samsung dot com
2023-02-27 14:06 ` schwab@linux-m68k.org
2023-09-22 4:29 ` akhilesh.k at samsung 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-30178-131@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@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).