From: "gliao.tw--- via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: 45376@debbugs.gnu.org
Cc: "emacs-devel@gnu.org" <emacs-devel@gnu.org>
Subject: bug#45376: 28.0.50; [Feature/Native-Comp] strange `ls` output in eshell loaded from eln
Date: Wed, 23 Dec 2020 01:59:42 +0000 [thread overview]
Message-ID: <gXxshNbsfXSuR7TY4y1dkyog50wGSOqc2dklpb72_CkduzqHDUsTtEr1F9fzOVuaIJKEcCsDMwO87VnqfxGjLzzMM6GGuNK9MZVi_kjCg_o=@pm.me> (raw)
[-- Attachment #1: Type: text/plain, Size: 686 bytes --]
Hi,
I checked the last updated feature/native-comp branch (commit 433ae7b0a5cedbcd7b0a1daf12846e38f00fd111) and identified a strange outputs from eln-compiled eshell.
The first attachment shows the `ls` command output under eshell loaded from elc, while the second attachment shows the same command, but much stranger output under eshell loaded from eln.
I have tested/complied the last updated code on Linux/x86-64, Linux/aarch64 (Debian Bullseye, GCC 10.2.1) and Windows (Msys2), all the test cases generate the same weird output from `ls` under eln-loaded eshell.
This issue does not happen on the code based at or before commit f244c21902
Thanks,
Kiong-Ge.
[-- Attachment #2: eshell-use-byte-code.png --]
[-- Type: image/png, Size: 21481 bytes --]
[-- Attachment #3: eshell-use-native-comp-eln.png --]
[-- Type: image/png, Size: 43043 bytes --]
next reply other threads:[~2020-12-23 1:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-23 1:59 gliao.tw--- via [this message]
2020-12-23 7:51 ` bug#45376: 28.0.50; [Feature/Native-Comp] strange `ls` output in eshell loaded from eln Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-12-23 15:27 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-12-23 17:10 ` gliao.tw--- via
2020-12-23 18:51 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-12-25 5:59 ` Lars Ingebrigtsen
2020-12-25 8:01 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-12-23 15:34 ` gliao.tw--- via
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='gXxshNbsfXSuR7TY4y1dkyog50wGSOqc2dklpb72_CkduzqHDUsTtEr1F9fzOVuaIJKEcCsDMwO87VnqfxGjLzzMM6GGuNK9MZVi_kjCg_o=@pm.me' \
--to=45376@debbugs.gnu.org \
--cc=emacs-devel@gnu.org \
--cc=gliao.tw@pm.me \
/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).