From: "Óscar Fuentes" <ofv@wanadoo.es>
To: emacs-devel@gnu.org
Subject: Re: igc: trying to chase a crash
Date: Mon, 25 Nov 2024 21:51:03 +0100 [thread overview]
Message-ID: <87v7wb11hk.fsf@telefonica.net> (raw)
In-Reply-To: 86zflngk0j.fsf@gnu.org
Eli Zaretskii <eliz@gnu.org> writes:
>> So does it make sense to run igc under gdb for obtaining backtraces when
>> it crashes?
>
> Yes, it does. Because if you hit a real segfault, it will stop again.
Ok, thanks.
> Fixed.
>
> How about if you say "make -k", so that we see all the problems at
> once, not one by one?
:-)
Loading mwheel...
Pure Lisp storage overflowed
Error: error ("Cannot continue, pure space overflowed")
defalias(mouse-wheel--get-scroll-window #[257 "\30127\0\10\203\16\0\302\1!\202\20\0\303 \304\1!\205\34\0\305\306\2!\307\"\310\1!\2054\0\311 \211@\1A\312\313\314\3\5#\5\315\316$\266\203\266\2020\206=\0\302\1!\207" [mouse-wheel-follow-mouse found mwheel-event-window selected-window window-live-p frame-parameter window-frame mouse-wheel-frame frame-live-p mouse-absolute-pixel-position walk-window-tree make-closure #[257 "\302\1\303\304\211$\211@\301X\205)\0\301\305\28X\205)\0\211A@\300X\205)\0\300\306\28X\205)\0\307\310\3\"\207" [V0 V1 window-edges nil t 2 3 throw found] 6 "\n\n(fn WINDOW-1)"] nil t] 11 "Return window for mouse wheel event EVENT.\nIf `mouse-wheel-follow-mouse' is non-nil, return the window that\nthe mouse pointer is over. Otherwise, return the currently\nactive window.\n\n
(fn EVENT)"])
load("mwheel")
(if (fboundp 'x-create-frame) (load "mwheel"))
load("loadup.el")
Cannot continue, pure space overflowed
ok, ok... setting SYSTEM_PURESIZE_EXTRA fixes that and the build
completes. But I'm surprised to be the first to report these problems.
Is the igc project dormant? Are there people interested on bug reports
about igc?
next prev parent reply other threads:[~2024-11-25 20:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-25 18:48 igc: trying to chase a crash Óscar Fuentes
2024-11-25 19:23 ` Eli Zaretskii
2024-11-25 19:53 ` Óscar Fuentes
2024-11-25 20:01 ` Eli Zaretskii
2024-11-25 20:51 ` Óscar Fuentes [this message]
2024-11-26 3:33 ` Eli Zaretskii
2024-11-26 5:17 ` Gerd Möllmann
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=87v7wb11hk.fsf@telefonica.net \
--to=ofv@wanadoo.es \
--cc=emacs-devel@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).