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 tdep/29408] [gdb, tdep/aarch64] FAIL: gdb.base/large-frame.exp: optimize=-O0: backtrace
Date: Thu, 04 Aug 2022 10:34:55 +0000 [thread overview]
Message-ID: <bug-29408-4717-RsmpgI7FGs@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29408-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=29408
--- Comment #1 from Tom de Vries <vries at gcc dot gnu.org> ---
Created attachment 14255
--> https://sourceware.org/bugzilla/attachment.cgi?id=14255&action=edit
Tentative patch
Fixes the failures:
...
Running /home/tdevries/gdb/src/gdb/testsuite/gdb.base/large-frame.exp ...
=== gdb Summary ===
# of expected passes 6
...
We do slightly overshoot:
...
$ gdb -q -batch ./outputs/gdb.base/large-frame/large-frame-O0 -ex "b func"
Breakpoint 1 at 0x400624
...
because according to the line info (which we can see if we compile
large-frame-2.c with debug info), the first insn after the prologue is
0x400620:
...
0000000000400610 <func>:
400610: d2880210 mov x16, #0x4010 //
#16400
400614: cb3063ff sub sp, sp, x16
400618: a9007bfd stp x29, x30, [sp]
40061c: 910003fd mov x29, sp
400620: 910043a0 add x0, x29, #0x10
400624: 97fffff0 bl 4005e4 <blah>
400628: 52800000 mov w0, #0x0 // #0
40062c: a9407bfd ldp x29, x30, [sp]
400630: d2880210 mov x16, #0x4010 //
#16400
400634: 8b3063ff add sp, sp, x16
400638: d65f03c0 ret
40063c: d503201f nop
...
but that is a pre-existing problem.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2022-08-04 10:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-26 6:48 [Bug tdep/29408] New: " vries at gcc dot gnu.org
2022-07-26 6:48 ` [Bug tdep/29408] " vries at gcc dot gnu.org
2022-08-04 10:34 ` vries at gcc dot gnu.org [this message]
2022-08-04 13:05 ` vries at gcc dot gnu.org
2022-08-04 13:24 ` 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-29408-4717-RsmpgI7FGs@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).