all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: BT Templeton <bpt@hcoop.net>
Cc: 11704@debbugs.gnu.org
Subject: bug#11704: 24.1.50; REL_ALLOC-related segfault on GNU/Linux
Date: Sat, 17 Aug 2019 15:06:37 -0700	[thread overview]
Message-ID: <87v9uvjvki.fsf@mouse.gnus.org> (raw)
In-Reply-To: <878vfqpxg4.fsf@olor.terpri.org> (BT Templeton's message of "Wed,  13 Jun 2012 20:08:11 -0400")

BT Templeton <bpt@hcoop.net> writes:

> If I build Emacs with REL_ALLOC enabled on a GNU/Linux system, it
> sometimes crashes with a segmentation fault apparently related to the
> `real_morecore' function used in ralloc.c.
>
> This is one backtrace I've gotten from a core dump of emacs -Q:
>
> (gdb) bt full
> #0  0x00007f248dd9b757 in kill () at ../sysdeps/unix/syscall-template.S:82
> No locals.
> #1  0x00000000004fa3ea in fatal_error_signal (sig=<optimized out>) at emacs.c:368
> No locals.
> #2  fatal_error_signal (sig=<optimized out>) at emacs.c:338
> No locals.
> #3  <signal handler called>
> No symbol table info available.
> #4  0x00007ffff2c197b0 in ?? ()
> No symbol table info available.
> #5  0x00000000005d3b4d in check_memory_limits () at vm-limit.c:185

(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 seven 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





      reply	other threads:[~2019-08-17 22:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-14  0:08 bug#11704: 24.1.50; REL_ALLOC-related segfault on GNU/Linux BT Templeton
2019-08-17 22:06 ` 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=87v9uvjvki.fsf@mouse.gnus.org \
    --to=larsi@gnus.org \
    --cc=11704@debbugs.gnu.org \
    --cc=bpt@hcoop.net \
    /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.