public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug testsuite/31232] [gdb/testsuite, ppc64le] FAIL: gdb.dwarf2/dw2-entry-points.exp: bt foo
Date: Thu, 11 Jan 2024 11:43:49 +0000	[thread overview]
Message-ID: <bug-31232-4717-eDHvnvmu9B@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-31232-4717@http.sourceware.org/bugzilla/>

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

--- Comment #1 from Tom de Vries <vries at gcc dot gnu.org> ---
Yep, the prologue skipper is activated.

For powerpc, it walks past some instructions.

For x86_64, it walks past no instructions.

The test-case passes with:
...
diff --git a/gdb/testsuite/gdb.dwarf2/dw2-entry-points.exp
b/gdb/testsuite/gdb.dwarf2/dw2-entry-points.exp
index f361820f72f..67d8f3e062e 100644
--- a/gdb/testsuite/gdb.dwarf2/dw2-entry-points.exp
+++ b/gdb/testsuite/gdb.dwarf2/dw2-entry-points.exp
@@ -180,8 +180,8 @@ if ![runto_main] {
 }

 # Try whether we can set and hit breakpoints at the entry_points.
-gdb_breakpoint "foo"
-gdb_breakpoint "foobar"
+gdb_breakpoint "*foo"
+gdb_breakpoint "*foobar"

 # Now hit the entry_point break point and check their call-stack.
 gdb_continue_to_breakpoint "foo"
...
which disables prologue walking.

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

  reply	other threads:[~2024-01-11 11:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-11 11:04 [Bug testsuite/31232] New: " vries at gcc dot gnu.org
2024-01-11 11:43 ` vries at gcc dot gnu.org [this message]
2024-01-11 12:56 ` [Bug testsuite/31232] " vries at gcc dot gnu.org
2024-01-11 15:04 ` cvs-commit at gcc dot gnu.org
2024-01-11 15:05 ` vries 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-31232-4717-eDHvnvmu9B@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: link
Be 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).