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/31592] [gdb/testsuite] gdb.dwarf2/dw2-epilogue-begin.exp drops epilogue_begin entry
Date: Tue, 02 Apr 2024 07:22:44 +0000	[thread overview]
Message-ID: <bug-31592-4717-RubkmKGhrO@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-31592-4717@http.sourceware.org/bugzilla/>

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

--- Comment #1 from Tom de Vries <vries at gcc dot gnu.org> ---
This:
...
diff --git a/gdb/testsuite/gdb.dwarf2/dw2-epilogue-begin.exp
b/gdb/testsuite/gdb.dwarf2/dw2-epilogue-begin.exp
index f646e23da62..7ae14fa9b5a 100644
--- a/gdb/testsuite/gdb.dwarf2/dw2-epilogue-begin.exp
+++ b/gdb/testsuite/gdb.dwarf2/dw2-epilogue-begin.exp
@@ -134,6 +134,7 @@ Dwarf::assemble $asm_file {
            DW_LNS_set_epilogue_begin
            DW_LNS_copy

+           DW_LNE_set_address "$main_start + $main_len"
            DW_LNE_end_sequence
        }
     }
...
prevents the entry from being dropped:
...
INDEX  LINE   REL-ADDRESS        UNREL-ADDRESS      IS-STMT PROLOGUE-END
EPILOGUE-BEGIN 
0      20     0x00000000004004b7 0x00000000004004b7 Y       Y            Y      
1      27     0x00000000004004be 0x00000000004004be Y                           
2      34     0x00000000004004d0 0x00000000004004d0 Y       Y                   
3      37     0x00000000004004de 0x00000000004004de Y                    Y      
4      38     0x00000000004004ec 0x00000000004004ec Y                           
5      43     0x00000000004004ef 0x00000000004004ef Y       Y                   
6      47     0x00000000004004fa 0x00000000004004fa Y                           
7      50     0x00000000004004ff 0x00000000004004ff Y                    Y      
8      END    0x000000000040050d 0x000000000040050d Y                           
...
but no longer exercises the corner case.

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

  parent reply	other threads:[~2024-04-02  7:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-02  6:37 [Bug testsuite/31592] New: " vries at gcc dot gnu.org
2024-04-02  6:38 ` [Bug testsuite/31592] " vries at gcc dot gnu.org
2024-04-02  7:22 ` vries at gcc dot gnu.org [this message]
2024-04-04 15:20 ` vries at gcc dot gnu.org
2024-04-04 19:17 ` blarsen at redhat dot com
2024-04-17 10:54 ` cvs-commit at gcc dot gnu.org
2024-04-17 10:55 ` 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-31592-4717-RubkmKGhrO@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).