public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "cel at us dot ibm.com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug gdb/29989] PowerPC, gdb fails to stop at printf call Date: Thu, 12 Jan 2023 17:35:36 +0000 [thread overview] Message-ID: <bug-29989-4717-XcSGF4T7Ct@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-29989-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=29989 --- Comment #1 from Carl E Love <cel at us dot ibm.com> --- I was given a suggestion of trying rbreak printf. When I run this command I get asked Make breakpoint pending on future shared library load? (y or [n]) after answering the question a buzillion times you eventually get back to the gdb prompt. <function, no debug info> 00000020.plt_call._dl_fatal_printf@@GLIBC_PRIVATE; Breakpoint 1062 at 0x7ffff7bdb9b4 <function, no debug info> _dl_fatal_printf@plt; (gdb) (gdb) (gdb) c Continuing. Breakpoint 157, 0x00000000100005a0 in 0000001b.plt_call.__printfieee128@@GLIBC_2.32 () not sure exactly where we are but if we do a few step commands we then see (gdb) s Single stepping until exit from function __printfieee128@plt, which has no line number information. (gdb) s Single stepping until exit from function __glink_PLTresolve, which has no line number information. ___ieee128_printf (format=0x10000920 "value is %d\n") at ../sysdeps/ieee754/ldbl-128ibm-compat/ieee128-printf.c:24 24 { (gdb) list 19 #include <stdarg.h> 20 #include <libio/libioP.h> 21 22 extern int 23 ___ieee128_printf (const char *format, ...) 24 { 25 va_list ap; 26 int done; 27 28 va_start (ap, format); not sure what all this means yet but thought is was interesting. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2023-01-12 17:35 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-01-12 1:05 [Bug gdb/29989] New: " cel at us dot ibm.com 2023-01-12 17:35 ` cel at us dot ibm.com [this message] 2023-01-12 17:40 ` [Bug gdb/29989] " cel at us dot ibm.com 2024-01-26 0:24 ` cel at linux dot ibm.com 2024-01-26 0:25 ` cel at linux dot ibm.com 2024-01-28 8:32 ` sam at gentoo dot org 2024-03-06 22:25 ` cel at linux dot ibm.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-29989-4717-XcSGF4T7Ct@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=gdb-prs@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: linkBe 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).