From: Tom Tromey <tom@tromey.com>
To: Tom Tromey <tom@tromey.com>
Cc: Guinevere Larsen <blarsen@redhat.com>,
Simon Marchi <simark@simark.ca>,
gdb-patches@sourceware.org
Subject: Re: [PATCH] gdb/dwarf2: Add support for DW_LNS_set_epilogue_begin in line-table
Date: Thu, 11 Jan 2024 10:02:49 -0700 [thread overview]
Message-ID: <87ttnjrefa.fsf@tromey.com> (raw)
In-Reply-To: <87r0iprrx3.fsf@tromey.com> (Tom Tromey's message of "Wed, 10 Jan 2024 10:59:04 -0700")
Guinevere> I don't see anything wrong with this test locally, I get 179 expected
Guinevere> passes. Could it be some difference in config?
Tom> FWIW it works for me on x86-64 Fedora 38, using the system gcc.
Tom> I was wondering if there could be a compiler difference but I see the
Tom> test uses a .s file, so maybe not.
I found out today that it fails in my ASAN build but not my regular build.
I didn't see any ASAN warnings in the log, though.
Tom
prev parent reply other threads:[~2024-01-11 17:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-21 10:29 Guinevere Larsen
2023-12-22 16:34 ` Tom Tromey
2023-12-22 16:56 ` Guinevere Larsen
2024-01-02 9:24 ` Guinevere Larsen
2024-01-10 16:57 ` Simon Marchi
2024-01-10 17:01 ` Guinevere Larsen
2024-01-10 17:59 ` Tom Tromey
2024-01-11 17:02 ` Tom Tromey [this message]
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=87ttnjrefa.fsf@tromey.com \
--to=tom@tromey.com \
--cc=blarsen@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=simark@simark.ca \
/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