From: Andrea Corallo <acorallo@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gerd.moellmann@gmail.com, 65455@debbugs.gnu.org
Subject: bug#65455: 30.0.50; Disassemble: error with "free-standing" native compiled function
Date: Sun, 27 Aug 2023 11:41:46 -0400 [thread overview]
Message-ID: <yp1zg2c4hmt.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <83fs44k3ig.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 27 Aug 2023 16:40:07 +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 09:34:47 -0400
>>
>> > If we want to support changes in the environment, I think it would be
>> > an impossibly high bar for such a minor feature.
>> >
>> > So perhaps the following would be enough:
>> >
>> > . find the source .el file of the compiled function
>>
>> That's the tricky part, this bug report is about compiling and
>> disassembling a function with no source file:
>
> Yes. I'm saying we should not try to support that case, because it's
> too hard.
Okay,
I pushed 91d2d8439bb into 29, please have a look if the working of the
error is okay.
Thanks
Andrea
next prev parent reply other threads:[~2023-08-27 15:41 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 [this message]
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
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=yp1zg2c4hmt.fsf@fencepost.gnu.org \
--to=acorallo@gnu.org \
--cc=65455@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=gerd.moellmann@gmail.com \
/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).