unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Sam Steingold <sds@gnu.org>
To: "Gerd Möllmann" <gerd.moellmann@gmail.com>
Cc: 57751@debbugs.gnu.org
Subject: bug#57751: 29.0.50; crash in GC
Date: Thu, 15 Sep 2022 12:35:40 -0400	[thread overview]
Message-ID: <lz5yhor3xf.fsf@3c22fb11fdab.ant.amazon.com> (raw)
In-Reply-To: <m2bkrhurym.fsf@Mini.fritz.box> ("Gerd Möllmann"'s message of "Thu, 15 Sep 2022 07:28:17 +0200")

> * Gerd Möllmann <treq.zbryyznaa@tznvy.pbz> [2022-09-15 07:28:17 +0200]:
>
> Sam Steingold <sds@gnu.org> writes:
>
>> I _think_ that Tramp does something with a BAD FD and corrupts the
>> memory (see my previous message: tramp appears to be broken recently).
>
> I can't exclude that as a possibility, of course, but I think it's
> unlikely that using Tramp can lead to a corruption of the C heap
> somehow.

I don't think Tramp itself if the culprit, but the underlying networking
code.

> Oh, another thing I forgot to mention: LLDB requires a magic spell for
> running terminal apps, instead of "run":
>
> process launch --tty -- -nw

thank you!

> Moving means grabbing the titlebar?

yep.

> I'm asking because of the "part = scroll_bar_nowhere" in the event.

No idea what this is.

> And, are you using scroll bars or are they off?

they are present on the screen but I never click on them, I merely use
them as a visual indicator of buffer position.

> I think I'll try next to reproduce this desktop loading/moving frame
> crash here.  When I get something, I'll bisect, and then let's see
> further.  I'll report back when I have something.

Thank you!

-- 
Sam Steingold (https://aphar.dreamwidth.org/) on darwin Ns 10.3.2113
https://lastingimpactpsychology.com https://steingoldpsychology.com
https://iris.org.il https://jihadwatch.org http://think-israel.org
Brain is invisible, but lack thereof is not.





  parent reply	other threads:[~2022-09-15 16:35 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-12 14:37 bug#57751: 29.0.50; crash in GC Sam Steingold
2022-09-13  5:20 ` Gerd Möllmann
2022-09-13 14:51   ` Sam Steingold
2022-09-14  5:46     ` Gerd Möllmann
2022-09-14 18:36       ` Sam Steingold
2022-09-15  5:28         ` Gerd Möllmann
2022-09-15  8:42           ` Gerd Möllmann
2022-09-15  8:48             ` Gerd Möllmann
2022-09-15 10:01               ` Gerd Möllmann
2022-09-15 12:10                 ` Eli Zaretskii
2022-09-15 15:12                   ` Gerd Möllmann
2022-09-15 16:48                 ` Sam Steingold
2022-09-15 22:25                 ` Gregory Heytings
2022-09-15 22:41                   ` Sam Steingold
2022-09-15 22:42                   ` Sam Steingold
2022-09-15 23:17                     ` Gregory Heytings
2022-09-16  5:40                       ` Gerd Möllmann
2022-09-19 16:26                         ` Sam Steingold
2022-09-20  4:32                           ` Gerd Möllmann
2022-09-15  9:23             ` Eli Zaretskii
2022-09-15  9:37               ` Gerd Möllmann
2022-09-15 16:45             ` Sam Steingold
2022-09-15 16:35           ` Sam Steingold [this message]
2022-09-14 11:30     ` Gerd Möllmann
2022-09-14 11:32       ` Gerd Möllmann
2022-09-14 18:20       ` Sam Steingold
2022-09-15  4:49         ` Gerd Möllmann

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=lz5yhor3xf.fsf@3c22fb11fdab.ant.amazon.com \
    --to=sds@gnu.org \
    --cc=57751@debbugs.gnu.org \
    --cc=gerd.moellmann@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).