unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Dmitry Gutov <dgutov@yandex.ru>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 22356@debbugs.gnu.org
Subject: bug#22356: 25.0.50; emacs-25 very crashy with ivy-mode
Date: Wed, 13 Jan 2016 01:27:29 +0300	[thread overview]
Message-ID: <56957DD1.4080805@yandex.ru> (raw)
In-Reply-To: <831t9mk5q6.fsf@gnu.org>

On 01/12/2016 09:33 PM, Eli Zaretskii wrote:

> Was anything else on your system updated lately?  Some library,
> perhaps, or some system component?

Only minor updates, as far as I know. I'm on Ubuntu 15.10, which is the 
current stable, but not LTS, distribution. In the last few days, I've 
updated from kernel 4.2.0-22 to 4.2.0-23.

But I've rebooted into the previous version now (it's kept as backup), 
and the problem is still there.

Other applications, however, haven't suddenly become all crashy, 
however. And I use a few (web browser, email client, file manager, video 
player, torrent client). On the sum, they must be more complex than 
Emacs, and they also use libc, I suppose.

 > The problems look quite basic, for
> example this:
>> Program received signal SIGABRT, Aborted.
>> 0x00007ffff14a5267 in __GI_raise (sig=sig@entry=6) at
>> ../sysdeps/unix/sysv/linux/raise.c:55
>> 55	../sysdeps/unix/sysv/linux/raise.c: No such file or directory.
>
> means that glibc detected an invalid pointer being passed to 'free'.
> It's glibc which raises SIGABRT here, AFAIU, and it does that because
> if that invalid 'free' call.

Yes. Another thing I've noticed is that problems sort of clustered by 
type: if I start Emacs many times and repeat the same process, similar 
backtraces could show up for a few times in a row, then change to a 
different kind of error (also repeated a few times), then back...

Another piece of the puzzle: if I run emacs -Q -L <paths to the few 
packages I thought to be responsible: ivy, flx, highlight-tail>, 
recreate ivy's configuration and try it again, the problem doesn't show.

Going to bisect my configuration now.





  reply	other threads:[~2016-01-12 22:27 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-12 12:59 bug#22356: 25.0.50; emacs-25 very crashy with ivy-mode Dmitry Gutov
     [not found] ` <handler.22356.B.145260358930042.ack@debbugs.gnu.org>
2016-01-12 13:04   ` bug#22356: Acknowledgement (25.0.50; emacs-25 very crashy with ivy-mode) Dmitry Gutov
2016-01-12 16:01     ` Eli Zaretskii
2016-01-12 16:11       ` Dmitry Gutov
2016-01-12 18:25         ` Eli Zaretskii
2016-01-12 14:26 ` bug#22356: 25.0.50; emacs-25 very crashy with ivy-mode Dmitry Gutov
2016-01-12 16:05   ` Eli Zaretskii
2016-01-12 16:48     ` Dmitry Gutov
2016-01-12 18:33       ` Eli Zaretskii
2016-01-12 22:27         ` Dmitry Gutov [this message]
2016-01-13  0:21           ` Dmitry Gutov
2016-01-13  1:10             ` Óscar Fuentes
2016-01-13  1:15               ` Óscar Fuentes
2016-01-13  1:22                 ` Dmitry Gutov
2016-01-13  1:36                   ` Óscar Fuentes
2016-01-15 15:23                     ` Eli Zaretskii
2016-01-16  9:22                       ` martin rudalics
2016-01-16 10:03                         ` Eli Zaretskii
2016-01-15 15:24                     ` Eli Zaretskii
2016-01-15 16:06                       ` Óscar Fuentes
2016-01-15 16:19                         ` Eli Zaretskii
2016-01-15 22:47                       ` Dmitry Gutov
2016-01-16  6:48                         ` 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=56957DD1.4080805@yandex.ru \
    --to=dgutov@yandex.ru \
    --cc=22356@debbugs.gnu.org \
    --cc=eliz@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).