public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug libc/30178] New: backtrace is not working on riscv
@ 2023-02-27 13:46 akhilesh.k at samsung dot com
  2023-02-27 13:47 ` [Bug libc/30178] " akhilesh.k at samsung dot com
                   ` (2 more replies)
  0 siblings, 3 replies; 4+ messages in thread
From: akhilesh.k at samsung dot com @ 2023-02-27 13:46 UTC (permalink / raw)
  To: glibc-bugs

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.

^ permalink raw reply	[flat|nested] 4+ messages in thread

* [Bug libc/30178] backtrace is not working on riscv
  2023-02-27 13:46 [Bug libc/30178] New: backtrace is not working on riscv akhilesh.k at samsung dot com
@ 2023-02-27 13:47 ` 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
  2 siblings, 0 replies; 4+ messages in thread
From: akhilesh.k at samsung dot com @ 2023-02-27 13:47 UTC (permalink / raw)
  To: glibc-bugs

https://sourceware.org/bugzilla/show_bug.cgi?id=30178

Akhilesh Kumar <akhilesh.k at samsung dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |akhilesh.k at samsung dot com,
                   |                            |akhipatel at gmail dot com

-- 
You are receiving this mail because:
You are on the CC list for the bug.

^ permalink raw reply	[flat|nested] 4+ messages in thread

* [Bug libc/30178] backtrace is not working on riscv
  2023-02-27 13:46 [Bug libc/30178] New: backtrace is not working on riscv akhilesh.k at samsung dot com
  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
  2 siblings, 0 replies; 4+ messages in thread
From: schwab@linux-m68k.org @ 2023-02-27 14:06 UTC (permalink / raw)
  To: glibc-bugs

https://sourceware.org/bugzilla/show_bug.cgi?id=30178

--- Comment #1 from Andreas Schwab <schwab@linux-m68k.org> ---
riscv uses the generic backtrace that depends on a working libgcc unwinder.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

^ permalink raw reply	[flat|nested] 4+ messages in thread

* [Bug libc/30178] backtrace is not working on riscv
  2023-02-27 13:46 [Bug libc/30178] New: backtrace is not working on riscv akhilesh.k at samsung dot com
  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
  2 siblings, 0 replies; 4+ messages in thread
From: akhilesh.k at samsung dot com @ 2023-09-22  4:29 UTC (permalink / raw)
  To: glibc-bugs

https://sourceware.org/bugzilla/show_bug.cgi?id=30178

Akhilesh Kumar <akhilesh.k at samsung dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |FIXED
             Status|NEW                         |RESOLVED

--- Comment #2 from Akhilesh Kumar <akhilesh.k at samsung dot com> ---
Now Bt is working with setup: gcc 13.1, glibc 2.37, binutils 2.40

-- 
You are receiving this mail because:
You are on the CC list for the bug.

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2023-09-22  4:29 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2023-02-27 13:46 [Bug libc/30178] New: backtrace is not working on riscv akhilesh.k at samsung dot com
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

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).