From: Pip Cet <pipcet@gmail.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 42832@debbugs.gnu.org, Paul Eggert <eggert@cs.ucla.edu>
Subject: bug#42832: 28.0.50; "Bus error" when compiling Emacs now on Debian bullseye
Date: Thu, 13 Aug 2020 10:05:57 +0000 [thread overview]
Message-ID: <CAOqdjBdngQ51Mc1jjOup8LKacTbho4bOg5wjvrgyOpQfSLRG9Q@mail.gmail.com> (raw)
In-Reply-To: <874kp7jzsf.fsf@gnus.org>
On Wed, Aug 12, 2020 at 9:54 PM Lars Ingebrigtsen <larsi@gnus.org> wrote:
> Pip Cet <pipcet@gmail.com> writes:
>
> > Same sysctl settings, too? In particular, address randomization
> > appears to be enabled, does this also happen if you disable it (echo 0
> > | sudo tee /proc/sys/kernel/randomize_va_space) ?
>
> Tried that now and rebuilt -- bus error in the same place, I think:
>
> #0 raise (sig=<optimized out>) at ../sysdeps/unix/sysv/linux/raise.c:50
> #1 0x0000555555597ad5 in terminate_due_to_signal
> (sig=sig@entry=7, backtrace_limit=backtrace_limit@entry=40) at emacs.c:408
> #2 0x0000555555597f6b in handle_fatal_signal (sig=sig@entry=7)
> at sysdep.c:1782
> #3 0x0000555555692d9d in deliver_thread_signal
> (sig=7, handler=0x555555597f60 <handle_fatal_signal>) at sysdep.c:1756
> #4 0x0000555555692e89 in deliver_fatal_thread_signal (sig=<optimized out>)
> at sysdep.c:1794
> #5 0x00007ffff5726140 in <signal handler called> ()
> at /lib/x86_64-linux-gnu/libpthread.so.0
> #6 vector_marked_p (v=0xc000000018000000) at alloc.c:3859
> #7 mark_object (arg=<optimized out>) at alloc.c:6607
> #8 0x00005555556d6d7e in mark_vectorlike (header=0x555555c34f10)
> at alloc.c:6280
I'm trying to reproduce your build environment vaguely, and while the
addresses don't match up perfectly that does indeed appear to be an
eagerly-rehashed hash table's ->hash vector.
This is a shot in the dark, but in my case, the table containing that
address is Vdbus_registered_objects_table. Can you check whether
that's true in your case, too? Something like "p
globals.f_Vdbus_registered_objects_table" in gdb (using the core dump
should be fine) should either produce 0x555555c34f15 or something
else. If it is dbus, can you try compiling without it?
next prev parent reply other threads:[~2020-08-13 10:05 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-12 17:12 bug#42832: 28.0.50; "Bus error" when compiling Emacs now on Debian bullseye Lars Ingebrigtsen
2020-08-12 18:22 ` Lars Ingebrigtsen
2020-08-12 18:30 ` Lars Ingebrigtsen
2020-08-12 18:50 ` Eli Zaretskii
2020-08-12 18:58 ` Lars Ingebrigtsen
2020-08-12 19:28 ` Lars Ingebrigtsen
2020-08-12 19:33 ` Lars Ingebrigtsen
2020-08-12 20:40 ` Paul Eggert
2020-08-12 20:47 ` Lars Ingebrigtsen
2020-08-12 21:42 ` Pip Cet
2020-08-12 21:54 ` Lars Ingebrigtsen
2020-08-13 10:05 ` Pip Cet [this message]
2020-08-13 10:12 ` Lars Ingebrigtsen
2020-08-13 10:15 ` Lars Ingebrigtsen
2020-08-13 14:08 ` Pip Cet
2020-08-14 11:48 ` Lars Ingebrigtsen
2020-08-14 12:05 ` Pip Cet
2020-08-14 12:34 ` Lars Ingebrigtsen
2020-08-14 14:24 ` Pip Cet
2020-08-14 15:01 ` Pip Cet
2020-08-14 15:37 ` Lars Ingebrigtsen
2020-08-14 19:08 ` Pip Cet
2020-08-14 19:35 ` Lars Ingebrigtsen
2020-08-14 21:10 ` Lars Ingebrigtsen
2020-08-14 21:48 ` Paul Eggert
2020-08-14 22:25 ` Pip Cet
2020-08-14 22:52 ` Paul Eggert
2020-08-12 22:00 ` Lars Ingebrigtsen
2020-08-12 18:34 ` Eli Zaretskii
2020-08-12 18:41 ` Lars Ingebrigtsen
2020-08-12 19:26 ` 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=CAOqdjBdngQ51Mc1jjOup8LKacTbho4bOg5wjvrgyOpQfSLRG9Q@mail.gmail.com \
--to=pipcet@gmail.com \
--cc=42832@debbugs.gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=larsi@gnus.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).