From: Lars Ingebrigtsen <larsi@gnus.org>
To: "Márcio Dick Smiderle" <marciodicksmiderle@gmail.com>
Cc: 21531@debbugs.gnu.org
Subject: bug#21531: 24.4; Segmentation fault in glib/emacs
Date: Sat, 17 Aug 2019 14:35:53 -0700 [thread overview]
Message-ID: <87mug7lbk6.fsf@mouse.gnus.org> (raw)
In-Reply-To: <CABd7hnrJkjxWRz2H2qa+zC_rFGZojczfgOA4AUXKgzd4igowNw@mail.gmail.com> ("Márcio Dick Smiderle"'s message of "Mon, 21 Sep 2015 15:55:16 -0300")
Márcio Dick Smiderle <marciodicksmiderle@gmail.com> writes:
> I was using emacs with lots of buffers of varied size (from some kbytes
> to 25 megabytes) for a couple of days and between some system
> hibernations.
> I have saved two core files. I can upload the xzipped core files to some
> server upon your request (35 and 58 MB).
>
> First backtrace (547MB core file):
>
> (gdb) bt full
> #0 0x00007f25d54df79b in raise (sig=sig@entry=11) at
> ../nptl/sysdeps/unix/sysv/linux/pt-raise.c:37
> resultvar = 0
> pid = <optimized out>
> #1 0x00000000004e9fc6 in terminate_due_to_signal (sig=sig@entry=11,
> backtrace_limit=backtrace_limit@entry=40) at emacs.c:378
> No locals.
> #2 0x00000000005023ae in handle_fatal_signal (sig=sig@entry=11) at
> sysdep.c:1630
> No locals.
(I'm going through old bug reports that have unfortunately gotten no
responses yet.)
This crash wasn't handled at the time, and as this was reported more
than three years ago, I don't think there's much chance of making any
progress here, so I'm closing this bug report. If you're still seeing
similar crashes in modern Emacs versions, please reopen.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
prev parent reply other threads:[~2019-08-17 21:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-21 18:55 bug#21531: 24.4; Segmentation fault in glib/emacs Márcio Dick Smiderle
2019-08-17 21:35 ` Lars Ingebrigtsen [this message]
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=87mug7lbk6.fsf@mouse.gnus.org \
--to=larsi@gnus.org \
--cc=21531@debbugs.gnu.org \
--cc=marciodicksmiderle@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.