From: Visuwesh <visuweshm@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 58232@debbugs.gnu.org
Subject: bug#58232: 29.0.50; alloc.c:879: assertion failed: 0 < item_size && 0 < nitems_incr_min && 0 <= n0 && -1 <= nitems_max
Date: Sun, 02 Oct 2022 10:00:22 +0530 [thread overview]
Message-ID: <87pmfaq23l.fsf@gmail.com> (raw)
In-Reply-To: <831qrrbfly.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 01 Oct 2022 20:47:37 +0300")
[-- Attachment #1: Type: text/plain, Size: 1182 bytes --]
[சனி அக்டோபர் 01, 2022] Eli Zaretskii wrote:
>> With a build with checking enabled, I get the following message when I
>> launch Emacs.
>>
>> % emacs -Q
>> alloc.c:879: Emacs fatal error: assertion failed: 0 < item_size && 0 < nitems_incr_min && 0 <= n0 && -1 <= nitems_max
>> Aborted
>>
>> However, if I attach gdb to Emacs and launch it, it starts just fine.
>
> Can you enable core files and produce a core dump? Then it can be
> debugged with GDB, and we could see the backtrace.
I attached the core dump to this mail. In case GMail mangles it, then
you can get it from http://ix.io/4c3V. Since gdb's list command showed
somewhere around SECCOMP_USABLE, I checked if Emacs was built with
seccomp with the following C program
#if defined HAVE_LINUX_SECCOMP_H && defined HAVE_LINUX_FILTER_H \
&& HAVE_DECL_SECCOMP_SET_MODE_FILTER \
&& HAVE_DECL_SECCOMP_FILTER_FLAG_TSYNC
# define SECCOMP_USABLE 1
#else
# define SECCOMP_USABLE 0
#endif
#include <stdio.h>
int
main(){
printf("%d\n", SECCOMP_USABLE);
}
and it printed 0.
[-- Attachment #2: core --]
[-- Type: application/octet-stream, Size: 524288 bytes --]
next prev parent reply other threads:[~2022-10-02 4:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-01 16:33 bug#58232: 29.0.50; alloc.c:879: assertion failed: 0 < item_size && 0 < nitems_incr_min && 0 <= n0 && -1 <= nitems_max Visuwesh
2022-10-01 17:47 ` Eli Zaretskii
2022-10-02 4:30 ` Visuwesh [this message]
2022-10-02 6:14 ` Eli Zaretskii
2022-10-02 6:56 ` Visuwesh
2022-10-02 7:02 ` Eli Zaretskii
2022-10-02 8:37 ` Visuwesh
2022-10-02 9:00 ` Eli Zaretskii
2022-10-02 9:17 ` Visuwesh
2022-10-02 9:42 ` Eli Zaretskii
2022-10-02 9:47 ` Visuwesh
2022-10-02 9:58 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87pmfaq23l.fsf@gmail.com \
--to=visuweshm@gmail.com \
--cc=58232@debbugs.gnu.org \
--cc=eliz@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.