From: Andy Moreton <andrewjmoreton@gmail.com>
To: 60996@debbugs.gnu.org
Subject: bug#60996: 29.0.60; Native compile fails to remove temp file for trampoline
Date: Tue, 24 Jan 2023 22:32:35 +0000 [thread overview]
Message-ID: <864jsfo96k.fsf@gmail.com> (raw)
In-Reply-To: <74d13c46-5b26-9dd8-45dc-32b7fda25421@gmail.com>
On Tue 24 Jan 2023, Eli Zaretskii wrote:
>> Cc: 60996@debbugs.gnu.org
>> Date: Tue, 24 Jan 2023 19:50:27 +0200
>> From: Eli Zaretskii <eliz@gnu.org>
>>
>> and I still don't have a clear picture regarding which code calls
>> delete-file and why. For example, the first backtrace above says that
>> comp--native-compile calls delete-file via some byte-compiled
>> function, not directly. But what is that byte-compiled function? can
>> you figure that out?
I cannot reproduce the problem any more - trying to examine things in
gdb did not produce enlightenment, as the problem seems to be timing
sensitive, so adding breakpoints or tracing in my experiments often
stopped the problem.
>> There is a direct call to delete-file in comp--native-compile, but is
>> that the call which fails? And if so, why does it fail? Which code
>> created the .eln file that comp--native-compile tries to delete?
From memory I think that involved compiling a trampoline, and
comp-spill-lap calling one of the comp-spill-lap methods, which was
probably
(cl-defmethod comp-spill-lap-function ((form list))
I cannot reproduce this any longer as I have updated various software,
so this bug can probably be closed (and reopened later if the problem
becomes visible again).
AndyM
next prev parent reply other threads:[~2023-01-24 22:32 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-21 22:12 bug#60996: 29.0.60; Native compile fails to remove temp file for trampoline Andy Moreton
2023-01-22 6:17 ` Eli Zaretskii
2023-01-22 12:51 ` Andy Moreton
2023-01-23 17:04 ` Andrea Corallo
2023-01-23 17:11 ` Eli Zaretskii
2023-01-26 16:50 ` Andrea Corallo
2023-01-26 18:38 ` Eli Zaretskii
2023-01-26 19:46 ` Andrea Corallo
2023-01-26 20:03 ` Eli Zaretskii
2023-01-26 20:25 ` Andrea Corallo
2023-01-27 13:00 ` Eli Zaretskii
2023-01-27 13:56 ` Andrea Corallo
2023-01-26 20:35 ` Eli Zaretskii
2023-01-27 9:51 ` Andrea Corallo
2023-01-28 21:15 ` Andy Moreton
2023-01-29 7:01 ` Eli Zaretskii
2023-01-29 7:23 ` Eli Zaretskii
2023-01-30 10:11 ` Andrea Corallo
2023-01-29 7:47 ` Eli Zaretskii
2023-01-29 11:37 ` Andy Moreton
2023-01-29 13:50 ` Eli Zaretskii
2023-01-29 13:50 ` Eli Zaretskii
2023-01-23 2:30 ` Andy Moreton
2023-01-23 14:58 ` Eli Zaretskii
2023-01-24 1:18 ` Andy Moreton
2023-01-24 12:56 ` Eli Zaretskii
2023-01-24 17:50 ` Eli Zaretskii
2023-01-24 19:12 ` Eli Zaretskii
2023-01-24 22:32 ` Andy Moreton [this message]
2023-01-25 11:58 ` Eli Zaretskii
2023-01-25 23:49 ` Andy Moreton
2023-01-26 6:51 ` Eli Zaretskii
2023-01-26 16:57 ` Andrea Corallo
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=864jsfo96k.fsf@gmail.com \
--to=andrewjmoreton@gmail.com \
--cc=60996@debbugs.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).