[Bug gdb/29989] PowerPC, gdb fails to stop at printf call
"cvs-commit at gcc dot gnu.org via Gdb-prs" <[email protected]>
| Newsgroups | gmane.comp.gdb.bugs.discuss |
|---|---|
| Message-ID | <[email protected]/bugzilla/> |
https://sourceware.org/bugzilla/show_bug.cgi?id=29989 --- Comment #8 from Sourceware Commits <cvs-commit at gcc dot gnu.org> --- The gdb-18-branch branch has been updated by Tom de Vries <[email protected]>: https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=ff4fd46f4d974ee525f7a3b514833ba38b02dd3f commit ff4fd46f4d974ee525f7a3b514833ba38b02dd3f Author: Tom de Vries <[email protected]> Date: Mon Aug 17 08:14:53 2026 +0200 [gdb/testsuite] Add xfail for failure to break on ppc printf With test-case gdb.server/sysroot.exp, we run into: ... (gdb) break printf^M Breakpoint 2 at 0x7ffff7c2045c^M (gdb) continue^M Continuing.^M [Inferior 1 (process 469972) exited normally]^M (gdb) FAIL: $exp: sysroot=local: continue to printf (the program exited) ... The problem is that while breakpoint is indeed set on printf: ... (gdb) b printf Breakpoint 2 at 0x7ffff7c2045c (gdb) disassemble 0x7ffff7c2045c Dump of assembler code for function printf@@GLIBC_2.17: ... the function that is called instead is __printfieee128. Glibc commit f05ab7c4a9 ("ldbl-128ibm-compat: Add local aliases for printf family symbols") should fix this, but that's available starting version 2.43. Add an xfail for older glibc (without backport of that patch). Tested on ppc64le-linux and x86_64-linux. Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=29989 (cherry picked from commit 3cdb0313346fa63a028de9e7c2129182cd36ad2e) -- You are receiving this mail because: You are on the CC list for the bug.