From: "Gerd Möllmann" <gerd.moellmann@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 65455@debbugs.gnu.org, Andrea Corallo <acorallo@gnu.org>
Subject: bug#65455: 30.0.50; Disassemble: error with "free-standing" native compiled function
Date: Thu, 26 Oct 2023 08:53:24 +0200 [thread overview]
Message-ID: <m2y1fp3me3.fsf@Pro.fritz.box> (raw)
In-Reply-To: <831qfojqg2.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 27 Aug 2023 21:22:21 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Andrea Corallo <acorallo@gnu.org>
>> Cc: gerd.moellmann@gmail.com, 65455@debbugs.gnu.org
>> Date: Sun, 27 Aug 2023 14:04:57 -0400
>>
>> Eli Zaretskii <eliz@gnu.org> writes:
>>
>> > It looks like a Windows-specific issue: the symbols produced by
>> > objdump here have a leading underscore:
>> >
>> > 6b341400 <_F666f6f_foo_0>:
>> > 6b341400: 57 push %edi
>> > 6b341401: 56 push %esi
>> > 6b341402: 53 push %ebx
>> >
>> > So I think the regexp should be "^.*<_?F666f6f_foo_0>:" instead.
>>
>> Yep agree, I think this bug was unrelated, could you please check that
>> ea5fd6c96bc works for you on Windows?
>
> Works, thanks.
I thinks this has been fixed, so I'm closing it.
prev parent reply other threads:[~2023-10-26 6:53 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-22 13:17 bug#65455: 30.0.50; Disassemble: error with "free-standing" native compiled function Gerd Möllmann
2023-08-22 13:29 ` Eli Zaretskii
2023-08-22 13:41 ` Gerd Möllmann
2023-08-22 15:39 ` Eli Zaretskii
2023-08-25 8:11 ` Andrea Corallo
2023-08-25 10:30 ` Eli Zaretskii
2023-08-25 11:43 ` Andrea Corallo
2023-08-25 11:47 ` Eli Zaretskii
2023-08-25 11:52 ` Andrea Corallo
2023-08-25 13:01 ` Eli Zaretskii
2023-08-25 14:11 ` Andrea Corallo
2023-08-25 14:56 ` Eli Zaretskii
2023-08-27 13:34 ` Andrea Corallo
2023-08-27 13:40 ` Eli Zaretskii
2023-08-27 15:41 ` Andrea Corallo
2023-08-27 14:43 ` Andrea Corallo
2023-08-27 16:21 ` Eli Zaretskii
2023-08-27 18:04 ` Andrea Corallo
2023-08-27 18:22 ` Eli Zaretskii
2023-10-26 6:53 ` Gerd Möllmann [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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2y1fp3me3.fsf@Pro.fritz.box \
--to=gerd.moellmann@gmail.com \
--cc=65455@debbugs.gnu.org \
--cc=acorallo@gnu.org \
--cc=eliz@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).