From: Lars Ingebrigtsen <larsi@gnus.org>
To: emacs-devel@gnu.org
Subject: Re: "corrupted size vs. prev_size"
Date: Tue, 12 Apr 2022 14:26:30 +0200 [thread overview]
Message-ID: <875ynewkqx.fsf@gnus.org> (raw)
In-Reply-To: <87a6cqwmo1.fsf@gnus.org> (Lars Ingebrigtsen's message of "Tue, 12 Apr 2022 13:45:02 +0200")
Lars Ingebrigtsen <larsi@gnus.org> writes:
> And I've now managed to catch a backtrace in gdb twice. The error
> happens here both times:
But now I got a real segfault somewhere else:
#0 0x00005555557210e9 in sweep_conses () at alloc.c:7119
#1 0x0000555555727187 in gc_sweep () at alloc.c:7384
#2 garbage_collect () at alloc.c:6235
#3 0x0000555555727651 in maybe_garbage_collect () at alloc.c:6085
#4 0x0000555555748665 in maybe_gc ()
at /home/larsi/src/emacs/trunk/src/lisp.h:5522
#5 Ffuncall (nargs=nargs@entry=2, args=args@entry=0x7fffffffd670)
at eval.c:2868
#6 0x00005555556c3856 in call1 (arg1=0x555579d44a5d, fn=0xf0f0)
at /home/larsi/src/emacs/trunk/src/lisp.h:3216
#7 timer_check_2 (idle_timers=<optimized out>, timers=<optimized out>)
at keyboard.c:4591
#8 timer_check () at keyboard.c:4653
#9 0x00005555556c3b65 in readable_events (flags=flags@entry=1)
at keyboard.c:3484
#10 0x00005555556c47a8 in get_input_pending (flags=flags@entry=1)
at keyboard.c:7225
#11 0x00005555556cb584 in detect_input_pending_run_timers (do_display=false)
at keyboard.c:10755
#12 read_char
(commandflag=1, map=0x55557836f8c3, prev_event=0x0, used_mouse_menu=0x7fffffffdb8b, end_time=0x0) at keyboard.c:2581
#13 0x00005555556cd899 in read_key_sequence
So it's just random out-of-bounds writing. (In gif_load somewhere,
apparently -- I'm able to trigger the problem with a gif-only test.)
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2022-04-12 12:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-12 10:59 "corrupted size vs. prev_size" Lars Ingebrigtsen
2022-04-12 11:14 ` Andreas Schwab
2022-04-12 11:23 ` Lars Ingebrigtsen
2022-04-12 11:26 ` Po Lu
2022-04-12 11:41 ` Lars Ingebrigtsen
2022-04-12 11:45 ` Lars Ingebrigtsen
2022-04-12 12:26 ` Lars Ingebrigtsen [this message]
2022-04-12 12:54 ` Lars Ingebrigtsen
2022-04-12 13:13 ` Lars Ingebrigtsen
2022-04-12 14:09 ` Lars Ingebrigtsen
2022-04-12 11:44 ` 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=875ynewkqx.fsf@gnus.org \
--to=larsi@gnus.org \
--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).