all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Visuwesh <visuweshm@gmail.com>
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 09:14:50 +0300	[thread overview]
Message-ID: <83lepyah0l.fsf@gnu.org> (raw)
In-Reply-To: <87pmfaq23l.fsf@gmail.com> (message from Visuwesh on Sun, 02 Oct 2022 10:00:22 +0530)

> From: Visuwesh <visuweshm@gmail.com>
> Cc: 58232@debbugs.gnu.org
> Date: Sun, 02 Oct 2022 10:00:22 +0530
> 
> >> 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.

The core file can only be debugged on your system, so posting it is
not useful.  You start GDB like this:

   $ gdb /path/to/emacs/src/emacs core

(where "core" should be replaced with the actual absolute file name of
the core file), and then you can type "bt" at GDB prompt to show the
backtrace from the abort site.

Note that the above will only be possible as long as you have the
original emacs binary which dumped core.  IOW, if you rebuild Emacs,
be sure to preserve the binary which aborted, or else GDB will refuse
to debug that.

Thanks.





  reply	other threads:[~2022-10-02  6:14 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
2022-10-02  6:14     ` Eli Zaretskii [this message]
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=83lepyah0l.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=58232@debbugs.gnu.org \
    --cc=visuweshm@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 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.