* Occasional Crash When Running `rgrep`
@ 2017-01-04 20:00 aditya siram
2017-01-04 20:03 ` aditya siram
0 siblings, 1 reply; 6+ messages in thread
From: aditya siram @ 2017-01-04 20:00 UTC (permalink / raw)
To: emacs-devel@gnu.org Development
[-- Attachment #1: Type: text/plain, Size: 1117 bytes --]
Hi,
Of late I've been getting occasional Emacs crashes with the following
backtrace:
$ emacs -nw
Fatal error 11: Segmentation fault
Backtrace:
emacs[0x4fbdb2]
emacs[0x4e3389]
emacs[0x4fa83e]
emacs[0x4faa43]
emacs[0x4faaaf]
/usr/lib/libpthread.so.0(+0x11080)[0x7f1ebfa42080]
emacs(re_search_2+0x38c)[0x53168c]
emacs[0x526c12]
emacs[0x527565]
emacs[0x527747]
emacs[0x554416]
emacs[0x58a32b]
emacs[0x553e7d]
emacs[0x55426b]
emacs[0x58a32b]
emacs[0x553e7d]
emacs[0x55426b]
emacs[0x58a32b]
emacs[0x553e7d]
emacs[0x55426b]
emacs[0x58a32b]
emacs[0x55426b]
emacs[0x5544dc]
emacs[0x552695]
emacs[0x554351]
emacs[0x58a32b]
emacs[0x55426b]
emacs[0x58a32b]
emacs[0x55426b]
emacs[0x58a32b]
emacs[0x55426b]
emacs[0x552de6]
emacs[0x42abca]
emacs[0x437f5f]
emacs[0x438087]
emacs[0x43c3ea]
emacs[0x440ca2]
emacs[0x43f105]
emacs[0x44a3c8]
emacs[0x44d00a]
emacs[0x460b9e]
...
Segmentation fault (core dumped)
I can't reproduce this minimally but it seems to happen when (1) I'm using
emacsclient, the above crashed during an `emacsclient -c` session, and (2)
when running some kind of file search, I usually use rgrep.
Thanks!
-deech
[-- Attachment #2: Type: text/html, Size: 1355 bytes --]
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Occasional Crash When Running `rgrep`
2017-01-04 20:00 Occasional Crash When Running `rgrep` aditya siram
@ 2017-01-04 20:03 ` aditya siram
2017-01-04 20:10 ` Eli Zaretskii
0 siblings, 1 reply; 6+ messages in thread
From: aditya siram @ 2017-01-04 20:03 UTC (permalink / raw)
To: emacs-devel@gnu.org Development
[-- Attachment #1: Type: text/plain, Size: 1668 bytes --]
I forgot to include the relevant version info, sorry:
$ emacs --version
GNU Emacs 25.1.1
Copyright (C) 2016 Free Software Foundation, Inc.
GNU Emacs comes with ABSOLUTELY NO WARRANTY.
You may redistribute copies of GNU Emacs
under the terms of the GNU General Public License.
For more information about these matters, see the file named COPYING.
$ uname -r
4.4.38-1-lts
2017-01-04 14:00 GMT-06:00 aditya siram <aditya.siram@gmail.com>:
> Hi,
> Of late I've been getting occasional Emacs crashes with the following
> backtrace:
> $ emacs -nw
> Fatal error 11: Segmentation fault
> Backtrace:
> emacs[0x4fbdb2]
> emacs[0x4e3389]
> emacs[0x4fa83e]
> emacs[0x4faa43]
> emacs[0x4faaaf]
> /usr/lib/libpthread.so.0(+0x11080)[0x7f1ebfa42080]
> emacs(re_search_2+0x38c)[0x53168c]
> emacs[0x526c12]
> emacs[0x527565]
> emacs[0x527747]
> emacs[0x554416]
> emacs[0x58a32b]
> emacs[0x553e7d]
> emacs[0x55426b]
> emacs[0x58a32b]
> emacs[0x553e7d]
> emacs[0x55426b]
> emacs[0x58a32b]
> emacs[0x553e7d]
> emacs[0x55426b]
> emacs[0x58a32b]
> emacs[0x55426b]
> emacs[0x5544dc]
> emacs[0x552695]
> emacs[0x554351]
> emacs[0x58a32b]
> emacs[0x55426b]
> emacs[0x58a32b]
> emacs[0x55426b]
> emacs[0x58a32b]
> emacs[0x55426b]
> emacs[0x552de6]
> emacs[0x42abca]
> emacs[0x437f5f]
> emacs[0x438087]
> emacs[0x43c3ea]
> emacs[0x440ca2]
> emacs[0x43f105]
> emacs[0x44a3c8]
> emacs[0x44d00a]
> emacs[0x460b9e]
> ...
> Segmentation fault (core dumped)
>
> I can't reproduce this minimally but it seems to happen when (1) I'm using
> emacsclient, the above crashed during an `emacsclient -c` session, and (2)
> when running some kind of file search, I usually use rgrep.
>
> Thanks!
> -deech
>
[-- Attachment #2: Type: text/html, Size: 2135 bytes --]
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Occasional Crash When Running `rgrep`
2017-01-04 20:03 ` aditya siram
@ 2017-01-04 20:10 ` Eli Zaretskii
2017-01-08 19:02 ` aditya siram
0 siblings, 1 reply; 6+ messages in thread
From: Eli Zaretskii @ 2017-01-04 20:10 UTC (permalink / raw)
To: aditya siram; +Cc: emacs-devel
> From: aditya siram <aditya.siram@gmail.com>
> Date: Wed, 4 Jan 2017 14:03:54 -0600
>
> I forgot to include the relevant version info, sorry:
> $ emacs --version
> GNU Emacs 25.1.1
> Copyright (C) 2016 Free Software Foundation, Inc.
> GNU Emacs comes with ABSOLUTELY NO WARRANTY.
> You may redistribute copies of GNU Emacs
> under the terms of the GNU General Public License.
> For more information about these matters, see the file named COPYING.
> $ uname -r
> 4.4.38-1-lts
>
> 2017-01-04 14:00 GMT-06:00 aditya siram <aditya.siram@gmail.com>:
>
> Hi,
> Of late I've been getting occasional Emacs crashes with the following backtrace:
> $ emacs -nw
> Fatal error 11: Segmentation fault
> Backtrace:
> emacs[0x4fbdb2]
Can you convert this to a human-readable backtrace with file names and
line numbers, using the method described in the node "Crashing" of the
Emacs user manual? Otherwise, it's hard to do anything useful with
this information.
Thanks.
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Occasional Crash When Running `rgrep`
2017-01-04 20:10 ` Eli Zaretskii
@ 2017-01-08 19:02 ` aditya siram
2017-01-08 20:33 ` Eli Zaretskii
0 siblings, 1 reply; 6+ messages in thread
From: aditya siram @ 2017-01-08 19:02 UTC (permalink / raw)
To: Eli Zaretskii; +Cc: emacs-devel@gnu.org Development
[-- Attachment #1: Type: text/plain, Size: 8441 bytes --]
It took a couple of day for it to happen again, but here's the human
readable backtrace:
Jan 08 13:01:55 deech-thinkpad systemd-coredump[25660]: Process 27577
(emacs) of user 1000 dumped core.
Stack trace of
thread 27577:
#0
0x00007efc14652f5f raise (libpthread.so.0)
#1
0x00000000004e33b1 terminate_due_to_signal (emacs-25.1)
#2
0x00000000004fa83e handle_fatal_signal (emacs-25.1)
#3
0x00000000004faa43 deliver_thread_signal (emacs-25.1)
#4
0x00000000004faaaf deliver_fatal_thread_signal (emacs-25.1)
#5
0x00007efc14653080 __restore_rt (libpthread.so.0)
#6
0x00000000004a9fa0 turn_on_face (emacs-25.1)
#7
0x00000000004ae0f2 tty_write_glyphs (emacs-25.1)
#8
0x000000000041904a update_frame_line (emacs-25.1)
#9
0x000000000041c866 update_frame_1 (emacs-25.1)
#10
0x000000000041e08e update_frame (emacs-25.1)
#11
0x0000000000450cd4 redisplay_internal (emacs-25.1)
#12
0x00000000004ed1db read_char (emacs-25.1)
#13
0x00000000004efba0 read_key_sequence (emacs-25.1)
#14
0x00000000004f16c6 command_loop_1 (emacs-25.1)
#15
0x0000000000552c32 internal_condition_case (emacs-25.1)
#16
0x00000000004e37ec command_loop_2 (emacs-25.1)
#17
0x0000000000552bd3 internal_catch (emacs-25.1)
#18
0x00000000004e3750 command_loop (emacs-25.1)
#19
0x00000000004e7d77 recursive_edit_1 (emacs-25.1)
#20
0x000000000050ef5f read_minibuf (emacs-25.1)
#21
0x000000000050f6df Fread_from_minibuffer (emacs-25.1)
#22
0x00000000005543c0 Ffuncall (emacs-25.1)
#23
0x000000000058a32b exec_byte_code (emacs-25.1)
#24
0x000000000055426b Ffuncall (emacs-25.1)
#25
0x000000000058a32b exec_byte_code (emacs-25.1)
#26
0x000000000055426b Ffuncall (emacs-25.1)
#27
0x00000000005555c8 Fapply (emacs-25.1)
#28
0x0000000000554351 Ffuncall (emacs-25.1)
#29
0x000000000058a32b exec_byte_code (emacs-25.1)
#30
0x000000000055426b Ffuncall (emacs-25.1)
#31
0x00000000005555c8 Fapply (emacs-25.1)
#32
0x0000000000554351 Ffuncall (emacs-25.1)
#33
0x000000000058a32b exec_byte_code (emacs-25.1)
#34
0x000000000055426b Ffuncall (emacs-25.1)
#35
0x000000000058a32b exec_byte_code (emacs-25.1)
#36
0x0000000000553358 apply_lambda (emacs-25.1)
#37
0x000000000055366f eval_sub (emacs-25.1)
#38
0x00000000005564cd Fprogn (emacs-25.1)
#39
0x0000000000553841 eval_sub (emacs-25.1)
#40
0x0000000000553fed Fprogn (emacs-25.1)
#41
0x000000000055426b Ffuncall (emacs-25.1)
#42
0x000000000055019a Ffuncall_interactively (emacs-25.1)
#43
0x0000000000554351 Ffuncall (emacs-25.1)
#44
0x0000000000550b07 Fcall_interactively (emacs-25.1)
#45
0x000000000055442a Ffuncall (emacs-25.1)
#46
0x000000000058a32b exec_byte_code (emacs-25.1)
#47
0x000000000055426b Ffuncall (emacs-25.1)
#48
0x000000000055452a call1 (emacs-25.1)
#49
0x00000000004f18c1 command_loop_1 (emacs-25.1)
#50
0x0000000000552c32 internal_condition_case (emacs-25.1)
#51
0x00000000004e37ec command_loop_2 (emacs-25.1)
#52
0x0000000000552bd3 internal_catch (emacs-25.1)
#53
0x00000000004e37a9 command_loop (emacs-25.1)
#54
0x00000000004e7d77 recursive_edit_1 (emacs-25.1)
#55
0x00000000004e80b8 Frecursive_edit (emacs-25.1)
#56
0x0000000000414fee main (emacs-25.1)
#57
0x00007efc13e92291 __libc_start_main (libc.so.6)
#58
0x0000000000415b5a _start (emacs-25.1)
Stack trace of
thread 27578:
#0
0x00007efc13f5148d poll (libc.so.6)
#1
0x00007efc17f6b786 n/a (libglib-2.0.so.0)
#2
0x00007efc17f6b89c g_main_context_iteration (libglib-2.0.so.0)
#3
0x00007efc17f6b8e1 n/a (libglib-2.0.so.0)
#4
0x00007efc17f930d5 n/a (libglib-2.0.so.0)
#5
0x00007efc14649454 start_thread (libpthread.so.0)
#6
0x00007efc13f5a7df __clone (libc.so.6)
Thanks!
-deech
On Wed, Jan 4, 2017 at 2:10 PM, Eli Zaretskii <eliz@gnu.org> wrote:
> > From: aditya siram <aditya.siram@gmail.com>
> > Date: Wed, 4 Jan 2017 14:03:54 -0600
> >
> > I forgot to include the relevant version info, sorry:
> > $ emacs --version
> > GNU Emacs 25.1.1
> > Copyright (C) 2016 Free Software Foundation, Inc.
> > GNU Emacs comes with ABSOLUTELY NO WARRANTY.
> > You may redistribute copies of GNU Emacs
> > under the terms of the GNU General Public License.
> > For more information about these matters, see the file named COPYING.
> > $ uname -r
> > 4.4.38-1-lts
> >
> > 2017-01-04 14:00 GMT-06:00 aditya siram <aditya.siram@gmail.com>:
> >
> > Hi,
> > Of late I've been getting occasional Emacs crashes with the following
> backtrace:
> > $ emacs -nw
> > Fatal error 11: Segmentation fault
> > Backtrace:
> > emacs[0x4fbdb2]
>
> Can you convert this to a human-readable backtrace with file names and
> line numbers, using the method described in the node "Crashing" of the
> Emacs user manual? Otherwise, it's hard to do anything useful with
> this information.
>
> Thanks.
>
[-- Attachment #2: Type: text/html, Size: 13052 bytes --]
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Occasional Crash When Running `rgrep`
2017-01-08 19:02 ` aditya siram
@ 2017-01-08 20:33 ` Eli Zaretskii
2017-01-08 21:19 ` aditya siram
0 siblings, 1 reply; 6+ messages in thread
From: Eli Zaretskii @ 2017-01-08 20:33 UTC (permalink / raw)
To: aditya siram; +Cc: emacs-devel
> From: aditya siram <aditya.siram@gmail.com>
> Date: Sun, 8 Jan 2017 13:02:21 -0600
> Cc: "emacs-devel@gnu.org Development" <emacs-devel@gnu.org>
>
> It took a couple of day for it to happen again, but here's the human readable backtrace:
> Jan 08 13:01:55 deech-thinkpad systemd-coredump[25660]: Process 27577 (emacs) of user 1000 dumped
> core.
>
> Stack trace of thread 27577:
> #0 0x00007efc14652f5f raise (libpthread.so.0)
> #1 0x00000000004e33b1 terminate_due_to_signal (emacs-25.1)
> #2 0x00000000004fa83e handle_fatal_signal (emacs-25.1)
> #3 0x00000000004faa43 deliver_thread_signal (emacs-25.1)
> #4 0x00000000004faaaf deliver_fatal_thread_signal (emacs-25.1)
> #5 0x00007efc14653080 __restore_rt (libpthread.so.0)
> #6 0x00000000004a9fa0 turn_on_face (emacs-25.1)
> #7 0x00000000004ae0f2 tty_write_glyphs (emacs-25.1)
> #8 0x000000000041904a update_frame_line (emacs-25.1)
> #9 0x000000000041c866 update_frame_1 (emacs-25.1)
> #10 0x000000000041e08e update_frame (emacs-25.1)
> #11 0x0000000000450cd4 redisplay_internal (emacs-25.1)
> #12 0x00000000004ed1db read_char (emacs-25.1)
> #13 0x00000000004efba0 read_key_sequence (emacs-25.1)
> #14 0x00000000004f16c6 command_loop_1 (emacs-25.1)
> #15 0x0000000000552c32 internal_condition_case (emacs-25.1)
> #16 0x00000000004e37ec command_loop_2 (emacs-25.1)
> #17 0x0000000000552bd3 internal_catch (emacs-25.1)
> #18 0x00000000004e3750 command_loop (emacs-25.1)
> #19 0x00000000004e7d77 recursive_edit_1 (emacs-25.1)
> #20 0x000000000050ef5f read_minibuf (emacs-25.1)
> #21 0x000000000050f6df Fread_from_minibuffer (emacs-25.1)
Thanks. This doesn't look like Emacs was running rgrep, did it?
I suggest to try the latest pretest of Emacs 25.2, it could be that
this problem is already fixed.
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Occasional Crash When Running `rgrep`
2017-01-08 20:33 ` Eli Zaretskii
@ 2017-01-08 21:19 ` aditya siram
0 siblings, 0 replies; 6+ messages in thread
From: aditya siram @ 2017-01-08 21:19 UTC (permalink / raw)
To: Eli Zaretskii; +Cc: emacs-devel@gnu.org Development
[-- Attachment #1: Type: text/plain, Size: 2039 bytes --]
Yeah, it wasn't running 'rgrep'. I guess any intuition I had about why this
is happening is completely wrong. I'll try the pretest.
Thanks!
On Sun, Jan 8, 2017 at 2:33 PM, Eli Zaretskii <eliz@gnu.org> wrote:
> > From: aditya siram <aditya.siram@gmail.com>
> > Date: Sun, 8 Jan 2017 13:02:21 -0600
> > Cc: "emacs-devel@gnu.org Development" <emacs-devel@gnu.org>
> >
> > It took a couple of day for it to happen again, but here's the human
> readable backtrace:
> > Jan 08 13:01:55 deech-thinkpad systemd-coredump[25660]: Process 27577
> (emacs) of user 1000 dumped
> > core.
> >
> > Stack trace of thread 27577:
> > #0 0x00007efc14652f5f raise (libpthread.so.0)
> > #1 0x00000000004e33b1 terminate_due_to_signal (emacs-25.1)
> > #2 0x00000000004fa83e handle_fatal_signal (emacs-25.1)
> > #3 0x00000000004faa43 deliver_thread_signal (emacs-25.1)
> > #4 0x00000000004faaaf deliver_fatal_thread_signal (emacs-25.1)
> > #5 0x00007efc14653080 __restore_rt (libpthread.so.0)
> > #6 0x00000000004a9fa0 turn_on_face (emacs-25.1)
> > #7 0x00000000004ae0f2 tty_write_glyphs (emacs-25.1)
> > #8 0x000000000041904a update_frame_line (emacs-25.1)
> > #9 0x000000000041c866 update_frame_1 (emacs-25.1)
> > #10 0x000000000041e08e update_frame (emacs-25.1)
> > #11 0x0000000000450cd4 redisplay_internal (emacs-25.1)
> > #12 0x00000000004ed1db read_char (emacs-25.1)
> > #13 0x00000000004efba0 read_key_sequence (emacs-25.1)
> > #14 0x00000000004f16c6 command_loop_1 (emacs-25.1)
> > #15 0x0000000000552c32 internal_condition_case (emacs-25.1)
> > #16 0x00000000004e37ec command_loop_2 (emacs-25.1)
> > #17 0x0000000000552bd3 internal_catch (emacs-25.1)
> > #18 0x00000000004e3750 command_loop (emacs-25.1)
> > #19 0x00000000004e7d77 recursive_edit_1 (emacs-25.1)
> > #20 0x000000000050ef5f read_minibuf (emacs-25.1)
> > #21 0x000000000050f6df Fread_from_minibuffer (emacs-25.1)
>
> Thanks. This doesn't look like Emacs was running rgrep, did it?
>
> I suggest to try the latest pretest of Emacs 25.2, it could be that
> this problem is already fixed.
>
[-- Attachment #2: Type: text/html, Size: 2747 bytes --]
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2017-01-08 21:19 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2017-01-04 20:00 Occasional Crash When Running `rgrep` aditya siram
2017-01-04 20:03 ` aditya siram
2017-01-04 20:10 ` Eli Zaretskii
2017-01-08 19:02 ` aditya siram
2017-01-08 20:33 ` Eli Zaretskii
2017-01-08 21:19 ` aditya siram
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).