public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "arnez at linux dot ibm.com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug backtrace/28313] New: [s390] "PC not saved" when debugging without binary Date: Tue, 07 Sep 2021 14:51:44 +0000 [thread overview] Message-ID: <bug-28313-4717@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=28313 Bug ID: 28313 Summary: [s390] "PC not saved" when debugging without binary Product: gdb Version: unknown Status: NEW Severity: normal Priority: P2 Component: backtrace Assignee: unassigned at sourceware dot org Reporter: arnez at linux dot ibm.com Target Milestone: --- Several people have seen a "PC not saved" error when trying to debug programs without an associated binary on s390x. One way this can be reproduced is by attaching to a program whose binary has been deleted: (gdb) attach 3272749 Attaching to process 3272749 No executable file now. warning: Could not load vsyscall page because no executable was specified 0x000003fffddcf186 in ?? () (gdb) display/i $pc 1: x/i $pc => 0x3fffddcf186: lghi %r1,-4096 (gdb) si PC not saved (gdb) p $pc $1 = (void (*)()) 0x3fffddcf18a Note that the "PC not saved" error prevents the printing of the auto-display expression in this case. -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2021-09-07 14:51 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-09-07 14:51 arnez at linux dot ibm.com [this message] 2021-09-16 17:32 ` [Bug backtrace/28313] " ulrich.weigand at de dot ibm.com 2021-09-16 17:49 ` keiths at redhat dot com 2024-02-02 15:37 ` cvs-commit at gcc dot gnu.org
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-28313-4717@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).