unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: gijs@hillenius.net (Gijs Hillenius)
To: Robert Pluim <rpluim@gmail.com>
Cc: 39207@debbugs.gnu.org
Subject: bug#39207: 28.0.50; crash when sending gnus message
Date: Tue, 21 Jan 2020 10:43:29 +0100	[thread overview]
Message-ID: <87tv4pdu0u.fsf@hillenius.net> (raw)
In-Reply-To: <m2muahqhme.fsf@gmail.com> (Robert Pluim's message of "Tue, 21 Jan 2020 10:32:57 +0100")

I started afresh, repeated the gnus mail bug I described in the previous
message, got emacs-snapshot to hang, stopped it with kill -SIGUSR2
emacs-snapshot,

and then ran 'bt' as requested.

Hope this helps. 




gdb /usr/bin/emacs-snapshot-x
GNU gdb (Debian 8.3.1-1) 8.3.1
Copyright (C) 2019 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
    <http://www.gnu.org/software/gdb/documentation/>.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/bin/emacs-snapshot-x...
(No debugging symbols found in /usr/bin/emacs-snapshot-x)
(gdb) run /usr/bin/emacs-snapshot-x
Starting program: /usr/bin/emacs-snapshot-x /usr/bin/emacs-snapshot-x
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7ffff120c700 (LWP 71008)]
[New Thread 0x7ffff0993700 (LWP 71009)]
[New Thread 0x7fffebfff700 (LWP 71010)]
[Detaching after vfork from child process 71011]
[Detaching after vfork from child process 71012]
[Detaching after vfork from child process 71013]
[Detaching after vfork from child process 71014]
[Detaching after vfork from child process 71015]
[Detaching after vfork from child process 71016]
[Detaching after vfork from child process 71017]
[Detaching after vfork from child process 71018]
[Detaching after vfork from child process 71019]
[Detaching after vfork from child process 71020]
[Detaching after vfork from child process 71021]
[Detaching after vfork from child process 71022]
[Detaching after vfork from child process 71023]
[Detaching after vfork from child process 71024]
[Detaching after vfork from child process 71025]
[Detaching after vfork from child process 71026]
[Detaching after vfork from child process 71027]
[Detaching after vfork from child process 71028]
[Detaching after vfork from child process 71029]
[Detaching after vfork from child process 71030]
[Detaching after vfork from child process 71031]
[Detaching after vfork from child process 71032]
[Detaching after vfork from child process 71033]
[Detaching after vfork from child process 71034]
[Detaching after vfork from child process 71035]
[Detaching after vfork from child process 71036]
[Detaching after vfork from child process 71037]
[Detaching after vfork from child process 71038]
[Detaching after vfork from child process 71039]
[Detaching after vfork from child process 71040]
[Detaching after vfork from child process 71041]
[Detaching after vfork from child process 71042]
[Detaching after vfork from child process 71043]
[Detaching after vfork from child process 71044]
[Detaching after vfork from child process 71045]
[Detaching after vfork from child process 71046]
[Detaching after vfork from child process 71047]
[Detaching after vfork from child process 71048]
[Detaching after vfork from child process 71056]
[Detaching after vfork from child process 71057]
[Detaching after vfork from child process 71059]
[Detaching after vfork from child process 71060]
[Detaching after vfork from child process 71061]
[Detaching after vfork from child process 71062]
[Detaching after vfork from child process 71063]
[Detaching after vfork from child process 71065]

Thread 1 "emacs-snapshot-" received signal SIGUSR2, User defined signal 2.
0x00005555555b51bc in ?? ()
(gdb) bt
#0  0x00005555555b51bc in ?? ()
#1  0x00005555555d3a32 in ?? ()
#2  0x00005555555d44b7 in ?? ()
#3  0x00005555555d44b7 in ?? ()
#4  0x00005555555d44b7 in ?? ()
#5  0x00005555555d44b7 in ?? ()
#6  0x00005555555d528e in ?? ()
#7  0x00005555555d559e in ?? ()
#8  0x00005555555eeb8c in ?? ()
#9  0x00005555555f373e in ?? ()
#10 0x00005555556f6dfa in ?? ()
#11 0x00005555555df723 in ?? ()
#12 0x000055555568943f in ?? ()
#13 0x000055555568bf5d in ?? ()
#14 0x000055555568d74c in ?? ()
#15 0x00005555556f6d76 in ?? ()
#16 0x000055555567e7a4 in ?? ()
#17 0x00005555556f6ccf in ?? ()
#18 0x000055555567e743 in ?? ()
#19 0x0000555555683b3f in ?? ()
#20 0x0000555555683e7b in ?? ()
#21 0x000055555559ec58 in ?? ()
#22 0x00007ffff562dbbb in __libc_start_main (main=0x55555559d4b0, argc=2, argv=0x7fffffffe268, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fffffffe258)
    at ../csu/libc-start.c:308
#23 0x000055555559f36a in ?? ()
(gdb) 





  reply	other threads:[~2020-01-21  9:43 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-20 16:28 bug#39207: 28.0.50; crash when sending gnus message Gijs Hillenius
2020-01-20 16:50 ` Robert Pluim
2020-01-21  9:06   ` Gijs Hillenius
2020-01-21  9:32     ` Robert Pluim
2020-01-21  9:43       ` Gijs Hillenius [this message]
2020-01-21 10:39         ` Robert Pluim
2020-01-21 10:44           ` Andreas Schwab
2020-01-21 10:46             ` Gijs Hillenius
2020-01-21 11:08             ` bug#39207: WITH dgb symbols " Gijs Hillenius
2020-01-21 13:36               ` Robert Pluim
2020-01-21 15:39               ` Eli Zaretskii
2020-01-21 16:11                 ` Gijs Hillenius
2020-01-21 17:06                   ` Robert Pluim
2020-01-22  7:17                     ` Gijs Hillenius
2020-01-22  7:47                       ` Robert Pluim
     [not found]                         ` <87lfpzsvq5.fsf@hillenius.net>
2020-01-22 12:12                           ` Robert Pluim
2020-01-22 16:13                             ` Eli Zaretskii
2020-01-22 16:58                               ` Robert Pluim
2020-01-22 17:37                                 ` Eli Zaretskii
2020-01-22 20:39                                   ` Robert Pluim
2020-01-22 20:57                                     ` Andreas Schwab
2020-01-22 21:15                                       ` bug#39207: WITH dgb symbols Re: bug✓39207: " Robert Pluim
2020-01-22 21:43                                         ` Andreas Schwab
2020-01-22 21:13                                     ` bug#39207: WITH dgb symbols Re: bug#39207: " Andreas Schwab
2020-01-23  7:52                                       ` Paul Eggert
2020-01-23  8:48                                         ` Robert Pluim
2020-01-23  9:02                                           ` Paul Eggert
2020-01-23  5:54 ` 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=87tv4pdu0u.fsf@hillenius.net \
    --to=gijs@hillenius.net \
    --cc=39207@debbugs.gnu.org \
    --cc=rpluim@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 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).