unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: martin rudalics <rudalics@gmx.at>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 41239@debbugs.gnu.org
Subject: bug#41239: GTK builds crashing in XTread_socket after deleting a frame
Date: Sat, 16 May 2020 10:45:10 +0200	[thread overview]
Message-ID: <4778e865-87c3-3c26-0bf6-61ec1f164842@gmx.at> (raw)
In-Reply-To: <83d075uisz.fsf@gnu.org>

 > Once again, all the crashes are inside memory-allocation functions,
 > which suggests some kind of memory corruption.

But we can't exclude that this corruption happens in the GTK code, I
presume.

 > Did someone try to run
 > this scenario under valgrind?

I don't have it installed and never used it.  So I'm afraid that
someone else would have to chime in.

martin





  reply	other threads:[~2020-05-16  8:45 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-13 17:42 bug#41239: GTK builds crashing in XTread_socket after deleting a frame martin rudalics
2020-05-13 18:04 ` Eli Zaretskii
2020-05-14  7:54   ` martin rudalics
2020-05-14 14:22     ` Eli Zaretskii
2020-05-15 18:07       ` martin rudalics
2020-05-15 18:58         ` Eli Zaretskii
2020-05-16  8:45           ` martin rudalics [this message]
2020-05-20  1:50           ` Noam Postavsky
2020-05-20  9:06             ` martin rudalics
2020-05-20 16:07             ` Eli Zaretskii
2020-05-22  1:23               ` Noam Postavsky
2020-05-22  9:31                 ` martin rudalics
2020-05-22 11:05                   ` Eli Zaretskii
2020-05-22 11:25                   ` Noam Postavsky
2020-05-22 12:08                     ` Eli Zaretskii
2020-05-22 12:22                       ` Noam Postavsky
2020-05-22 12:37                         ` Eli Zaretskii
2020-05-25  0:31                           ` Noam Postavsky
2020-09-27 14:43                             ` Lars Ingebrigtsen
2020-05-22 13:03                     ` martin rudalics
     [not found]                       ` <87d06vl5le.fsf@gmail.com>
     [not found]                         ` <83r1vb189z.fsf@gnu.org>
2020-05-23 12:08                           ` Noam Postavsky
2020-05-23 12:38                             ` martin rudalics
2020-05-25  0:11                               ` Noam Postavsky
2020-05-26  8:03                                 ` martin rudalics

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=4778e865-87c3-3c26-0bf6-61ec1f164842@gmx.at \
    --to=rudalics@gmx.at \
    --cc=41239@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).