From: Eli Zaretskii <eliz@gnu.org>
To: "Рабочая Почта" <work.mail.for.me.tgg@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Porting Emacs on new platform.
Date: Wed, 15 Sep 2021 09:05:57 +0300 [thread overview]
Message-ID: <831r5qcr0a.fsf@gnu.org> (raw)
In-Reply-To: <CAFPVqnS9uw+af0jZ+sQbDtee3OdYFV8J=CHUW9VGBHnE6y40gg@mail.gmail.com> (work.mail.for.me.tgg@gmail.com)
> From: Рабочая Почта
> <work.mail.for.me.tgg@gmail.com>
> Date: Wed, 15 Sep 2021 01:27:55 +0300
>
> Could you explain how a portable dumper Emacs works (bootstrap-emacs.pdmp) and where it is placed in
> sources?
The portable dumper code is mainly in pdumper.c and pdumper.h.
> I just haven't time to examine all the source code. Forgive me for that.
> It crashes. That's okay, because I'm with my protege porting Emacs to a new platform (e2k).
What is special about that platform? Which OS kernel and what C
library are you using to build Emacs? Is e2k similar to any other
common Posix platforms?
> Here are logs with errors.
>
> Wrong type argument: listp, make[1]: * [Makefile:824: bootstrap-emacs.pdmp] Ошибка
> сегментированияmake[1]: выход из каталога ((exit from directory)) «/root/emacs-27.2/src»make: *
> [Makefile:424: src] Ошибка ((error)) 2
>
> Wrong type argument: listp, make[1]: *** [Makefile:824: bootstrap-emacs.pdmp] Segmentation fault
> make[1]: выход из каталога ((exit from directory)) «/home/ddrdmakar/emacs/emacs-27.2/src»
> make: *** [Makefile:424: src] Ошибка ((error)) 2
These just say Emacs segfaulted, but not much else. If there are
other messages around this one, please show them as well.
> With --with-dumping=none it builds successfully, it works, but crashes sometimes. That will be fixed by
> simple debugging.
Regardless of whether it works with pdumper or not, the first step
towards understanding the problem is to run the failing command line
under GDB and getting the backtrace from the crash site, preferably
also understanding what was the immediate cause of the crash. Only
then it would be possible to tell whether the code in pdumper.c is
part of the issue.
> BTW, could you send me instructions about working with your repo me to merge changes right? I mean to
> give our changes to you properly .
We prefer patches in "git format-patch" form, but if that's hard for
you, diffs produced by the Diff utility will also be okay. See the
file CONTRIBUTE for more about this.
Thank you for your interest in Emacs.
next prev parent reply other threads:[~2021-09-15 6:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-14 22:27 Porting Emacs on new platform Рабочая Почта
2021-09-15 1:15 ` Po Lu
2021-09-15 21:32 ` Рабочая Почта
2021-09-16 3:14 ` Po Lu
2021-09-16 5:22 ` Eli Zaretskii
2021-09-15 6:05 ` Eli Zaretskii [this message]
2021-09-15 22:20 ` Рабочая Почта
2021-09-15 22:49 ` Stephen Berman
2021-09-16 7:30 ` Andreas Schwab
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=831r5qcr0a.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=work.mail.for.me.tgg@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).