all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Thierry Volpiatto <thievol@posteo.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: larsi@gnus.org, 55832@debbugs.gnu.org
Subject: bug#55832: 28.1; Emacs crashes when using tramp from helm in emacs-29
Date: Thu, 09 Jun 2022 15:18:55 +0000	[thread overview]
Message-ID: <87zgilamm8.fsf@posteo.net> (raw)
In-Reply-To: <83r13y2dhz.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 870 bytes --]


Eli Zaretskii <eliz@gnu.org> writes:

>> From: Thierry Volpiatto <thievol@posteo.net>
>> Cc: Lars Ingebrigtsen <larsi@gnus.org>, 55832@debbugs.gnu.org
>> Date: Thu, 09 Jun 2022 10:42:57 +0000
>> 
>> 
>> > So Mattias's changes could only help in this case if the complete
>> > backtrace will show recursive calls to print_object etc.
>> 
>> Let me know what you want exactly for the complete backtrace.
>
> This:
>
>   (gdb) thread 1
>   (gdb) bt
>
> You said earlier the backtrace produced by that is huge, so I thought
> maybe just looking at the immediate cause of the segfault could give
> us enough info.  But now we need to see all of it.

Can't send here by mail it is too big 12.8M with 130303 frames, here a
link to the output file:

https://gist.github.com/thierryvolpiatto/17ee2c5631d0849e57a794e4663b71a5

Thanks.

-- 
Thierry

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 686 bytes --]

  reply	other threads:[~2022-06-09 15:18 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-07 15:16 bug#55832: 28.1; Emacs crashes when using tramp from helm in emacs-29 Thierry Volpiatto
2022-06-07 16:08 ` Eli Zaretskii
2022-06-07 17:02   ` Thierry Volpiatto
2022-06-07 17:18     ` Eli Zaretskii
2022-06-07 18:33       ` Thierry Volpiatto
2022-06-07 18:53         ` Eli Zaretskii
2022-06-07 19:20   ` Thierry Volpiatto
2022-06-08 13:01     ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-08 16:30     ` Eli Zaretskii
2022-06-08 18:17       ` Lars Ingebrigtsen
2022-06-08 18:25         ` Eli Zaretskii
2022-06-09 10:34           ` Lars Ingebrigtsen
2022-06-09 10:42           ` Thierry Volpiatto
2022-06-09 13:05             ` Eli Zaretskii
2022-06-09 15:18               ` Thierry Volpiatto [this message]
2022-06-09 15:29                 ` Lars Ingebrigtsen
2022-06-09 16:36                 ` Eli Zaretskii
2022-06-09 16:51                   ` Thierry Volpiatto
2022-06-09 17:48                     ` Eli Zaretskii
2022-06-09 18:28                       ` Thierry Volpiatto
2022-06-09 18:55                         ` Eli Zaretskii
2022-06-10  7:53                           ` Michael Albinus
2022-06-10 10:00                             ` Thierry Volpiatto
2022-06-10 12:20                               ` Michael Albinus
2022-06-11  6:14                                 ` Thierry Volpiatto
2022-06-11 19:27                                   ` Michael Albinus
2022-06-11 19:46                                     ` Thierry Volpiatto
2022-06-11 20:07                                       ` Michael Albinus
2022-06-11 20:12                                         ` Thierry Volpiatto
2022-06-12 18:16                                         ` Thierry Volpiatto
2022-06-14 11:39                                           ` Michael Albinus
2022-06-14 11:49                                             ` Thierry Volpiatto
2022-06-09 15:37               ` Thierry Volpiatto
2022-06-14 11:05 ` Michael Albinus
2022-06-14 11:36   ` Thierry Volpiatto
2022-06-14 11:44     ` Michael Albinus
2022-06-14 17:42 ` Michael Albinus
2022-06-16 17:27 ` Michael Albinus
2022-06-16 18:11   ` Thierry Volpiatto
2022-06-17 16:54     ` Michael Albinus
2022-06-17 17:10       ` Thierry Volpiatto
2022-06-19 14:25         ` Michael Albinus
2022-06-19 16:21           ` Thierry Volpiatto
2022-06-19 17:51             ` Michael Albinus
2022-06-21  8:24             ` Michael Albinus
2022-06-21  9:35               ` Thierry Volpiatto

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=87zgilamm8.fsf@posteo.net \
    --to=thievol@posteo.net \
    --cc=55832@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=larsi@gnus.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.