From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id C152D3858D32; Mon, 27 Feb 2023 13:46:44 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org C152D3858D32 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1677505604; bh=/jTgoT/Kwp+WW9F01naw8l9vPmM0QzD0ky8WJriYadY=; h=From:To:Subject:Date:From; b=mDgwgiTIBPjQoW8tvkoW5RGrr2qLQtnlkCiH9zux09+14dn3AjzJn+WB2vIqra8T2 vWwvCmoeBndQcjiIfVX0dHl00ZI1QczSTYBjnbEGiRIjsGfGH73gg7CenJp/bWRkLQ 0bTIeX1WdlTs0JihvRfN8EGY93ZnPqhvSvXTGGsQ= From: "akhilesh.k at samsung dot com" 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 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: glibc X-Bugzilla-Component: libc X-Bugzilla-Version: 2.36 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: akhilesh.k at samsung dot com X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter cc target_milestone Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://sourceware.org/bugzilla/show_bug.cgi?id=3D30178 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=20 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.=20 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=20 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 ret= urn depth 1=20 $riscv64-unknown-linux-gnu-gcc -march=3Drv64g -o backtrace -rdynamic backtrace.c=20 even checked with and without fp(-fno-omit-frame-pointer/--omit-frame-point= er) $./backtrace 3 backtrace() returned 1 addresses ./backtrace(myfunc3+0x18) [0x10b58]=20 $uname -a Linux buildroot 5.4.228 #1 SMP Wed Jan 18 13:15:58 IST 2023 riscv64 GNU/Lin= ux is this expected because for riscv I am able to find any separate backtrace implementation in glibc/sysdeps like arm.=20=20 Also In glibc release note such fail case for riscv.=20 https://sourceware.org/glibc/wiki/Release/2.36 https://sourceware.org/glibc/wiki/Release/2.33 --=20 You are receiving this mail because: You are on the CC list for the bug.=