From: Konstantin Kharlamov <hi-angel@yandex.ru>
To: 61960@debbugs.gnu.org
Subject: bug#61960: 30.0.50; Unexec build reliably crashes during loadup
Date: Sat, 04 Mar 2023 23:26:31 +0300 [thread overview]
Message-ID: <16c908b437880c83d5d07cebfbe817e0dca12510.camel@yandex.ru> (raw)
In-Reply-To: <d69421cb4b834331463ca60fca94e8b8efaaa320.camel@yandex.ru>
On Sat, 2023-03-04 at 23:05 +0300, Konstantin Kharlamov wrote:
> So, I kind of reproduced the problem… But it doesn't happen reliably.
>
> I reconfigured the build with the exact flags, ran `make clean` and `make`,
> and
> it did fail with a `free(): invalid pointer`.
>
> However, entering the `src/` dir and running `./temacs --batch -l loadup --
> temacs=bootstrap` doesn't reproduce crash, it finishes successfully.
>
> Gotta figure out under what exactly conditions crash happens.
UPD: did find the command that crashes:
./temacs --__aslr-disabled -batch -l loadup --temacs=dump
I think this command is run internally by `temacs`. I found it by running a bpftrace command alongside the build:
sudo bpftrace -e 'tracepoint:syscalls:sys_enter_exec*{ printf("pid: %d, comm: %s, args: ", pid, comm); join(args->argv); }'
next prev parent reply other threads:[~2023-03-04 20:26 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-04 14:55 bug#61960: 30.0.50; Unexec build reliably crashes during loadup Eli Zaretskii
2023-03-04 19:50 ` Konstantin Kharlamov
2023-03-04 19:51 ` Konstantin Kharlamov
2023-03-04 20:05 ` Konstantin Kharlamov
2023-03-04 20:26 ` Konstantin Kharlamov [this message]
2023-03-05 5:52 ` Eli Zaretskii
[not found] ` <xjf4jr0xkar.fsf@ma.sdf.org>
2023-03-04 21:56 ` Konstantin Kharlamov
2023-03-04 22:00 ` Konstantin Kharlamov
2023-03-04 22:08 ` Konstantin Kharlamov
2023-03-04 23:38 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-03-05 5:59 ` Eli Zaretskii
[not found] ` <xjf7cvtx0q0.fsf@ma.sdf.org>
2023-03-06 18:29 ` Eli Zaretskii
2023-03-07 14:59 ` Andrea Corallo
2023-03-07 15:33 ` Eli Zaretskii
2023-03-11 7:22 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
[not found] ` <xjfpm9es4qe.fsf@ma.sdf.org>
2023-03-12 23:49 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
[not found] ` <xjf3566s29a.fsf@ma.sdf.org>
2023-03-15 13:56 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-03-15 14:26 ` Eli Zaretskii
2023-03-16 0:30 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-03-16 6:25 ` Eli Zaretskii
[not found] ` <xjfv8j2qe69.fsf@ma.sdf.org>
2023-03-16 0:33 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-03-16 6:26 ` Eli Zaretskii
2023-03-05 5:46 ` Eli Zaretskii
2023-07-02 1:50 ` Konstantin Kharlamov
2023-07-02 2:27 ` Konstantin Kharlamov
2023-07-02 5:52 ` Eli Zaretskii
2023-07-02 11:32 ` Konstantin Kharlamov
2023-07-02 11:54 ` Konstantin Kharlamov
2023-07-02 14:10 ` Konstantin Kharlamov
2023-07-21 16:09 ` Konstantin Kharlamov
2023-07-21 16:30 ` Eli Zaretskii
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=16c908b437880c83d5d07cebfbe817e0dca12510.camel@yandex.ru \
--to=hi-angel@yandex.ru \
--cc=61960@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).