From: Eli Zaretskii <eliz@gnu.org>
To: Frank Terbeck <ft@bewatermyfriend.org>
Cc: 37671@debbugs.gnu.org
Subject: bug#37671: 27.0.50; Segmentation fault with --fg-daemon on Linux
Date: Thu, 05 Mar 2020 09:19:02 +0200 [thread overview]
Message-ID: <83y2sfuv4p.fsf@gnu.org> (raw)
In-Reply-To: <87imk85bnb.fsf@ft.bewatermyfriend.org> (message from Frank Terbeck on Sat, 15 Feb 2020 12:32:24 +0100)
> From: Frank Terbeck <ft@bewatermyfriend.org>
> Cc: 37671@debbugs.gnu.org
> Date: Sat, 15 Feb 2020 12:32:24 +0100
>
> Eli Zaretskii wrote:
> [...]
> >> Okay! Applying the patch now. We'll see how this goes!
> >
> > Any news on this?
>
> I've been running Emacs with this patch applied in gdb, like I did be-
> fore. I've had no crashes the last two weeks. Since the issue comes up
> very seldom, I'd like to give it a fair bit more time before calling it
> solved. The first time after reporting it took the issue took three
> months to rear its ugly head again. :)
I take it that the crash still didn't happen, is that true? If so,
maybe I should go ahead and install the change?
Thanks.
next prev parent reply other threads:[~2020-03-05 7:19 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-09 1:55 bug#37671: 27.0.50; Segmentation fault with --fg-daemon on Linux Frank Terbeck
2019-10-10 11:03 ` Eli Zaretskii
2019-10-10 18:27 ` Frank Terbeck
2020-01-08 3:23 ` Frank Terbeck
2020-01-08 16:28 ` Eli Zaretskii
2020-01-08 16:39 ` Frank Terbeck
2020-02-01 2:28 ` Frank Terbeck
2020-02-01 8:33 ` Eli Zaretskii
2020-02-01 2:43 ` Frank Terbeck
2020-02-01 8:46 ` Eli Zaretskii
2020-02-01 11:28 ` Frank Terbeck
2020-02-01 12:04 ` Eli Zaretskii
2020-02-01 12:49 ` Frank Terbeck
2020-02-01 13:08 ` Eli Zaretskii
2020-02-01 14:32 ` Frank Terbeck
2020-02-15 8:28 ` Eli Zaretskii
2020-02-15 11:32 ` Frank Terbeck
2020-03-05 7:19 ` Eli Zaretskii [this message]
2020-03-06 0:09 ` Frank Terbeck
2020-03-06 7:51 ` Eli Zaretskii
2019-10-10 20:56 ` Paul Eggert
2019-10-11 7:02 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83y2sfuv4p.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=37671@debbugs.gnu.org \
--cc=ft@bewatermyfriend.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.