all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
To: 16710@debbugs.gnu.org
Subject: bug#16710: 24.3.50; emacs crash.
Date: Mon, 10 Feb 2014 11:17:20 -0500	[thread overview]
Message-ID: <87fvnr6iy7.fsf@lifelogs.com> (raw)
In-Reply-To: <87iosnawu0.fsf@yahoo.fr>

On Mon, 10 Feb 2014 15:36:50 +0100 Nicolas Richard <theonewiththeevillook@yahoo.fr> wrote: 

NR> I couldn't reproduce, sorry. I'll set gnutls-log-level to 2 for a while,
NR> in the hope I can "reproduce" after some more waiting.

NR> Btw, I thought that TLS was not involved in the crash, because it
NR> happens after this:
NR> #20 <signal handler called>
NR> #21 0xb77fa424 in __kernel_vsyscall ()
NR> #22 0xb64ad9c7 in __GI_raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:63
NR> #23 0xb64af1e6 in __GI_abort () at abort.c:90
NR> #24 0xb64ec545 in __libc_message (do_abort=2, fmt=0xb65e3e14 "*** glibc detected *** %s: %s: 0x%s ***\n") at ../sysdeps/unix/sysv/linux/libc_fatal.c:197
NR> #25 0xb64f2d20 in malloc_printerr (action=<optimized out>, str=<optimized out>, ptr=0xd0f6a68) at malloc.c:4949
NR> #26 0xb64f4930 in _int_malloc (av=0xb6625440 <main_arena>, bytes=65536) at malloc.c:3433
NR> #27 0xb64f6019 in __GI___libc_malloc (bytes=65536) at malloc.c:2858
NR> #28 0x081aabaf in xmalloc (size=65536) at alloc.c:677

NR> Do I read that wrong ?

I thought I saw a problem in the ASN.1 memory deallocation in GnuTLS but
I may have simply misunderstood the stack trace.  I'm not very good at
debugging Emacs crashes, sorry.

Ted






  reply	other threads:[~2014-02-10 16:17 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-10 14:03 bug#16710: 24.3.50; emacs crash Nicolas Richard
2014-02-10 14:18 ` Ted Zlatanov
2014-02-10 14:36   ` Nicolas Richard
2014-02-10 16:17     ` Ted Zlatanov [this message]
2014-02-10 16:46       ` Nicolas Richard
2018-06-15 11:51 ` Noam Postavsky
2019-06-30  5:06 ` Stefan Kangas
2019-06-30 10:32   ` Nicolas Richard
2019-06-30 22:31     ` Stefan Kangas
2019-06-30 22:33       ` Stefan Kangas

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=87fvnr6iy7.fsf@lifelogs.com \
    --to=tzz@lifelogs.com \
    --cc=16710@debbugs.gnu.org \
    --cc=bug-gnu-emacs@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 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.