From: nljlistbox2@gmail.com (N. Jackson)
To: Eli Zaretskii <eliz@gnu.org>
Cc: eric@ericabrahamsen.net, larsi@gnus.org, 28596@debbugs.gnu.org
Subject: bug#28596: 26.0.60; Gnus gets into an ambiguous plugged/unplugged state that prevents retrieval of news
Date: Wed, 04 Jul 2018 14:03:17 -0400 [thread overview]
Message-ID: <8736wy7uai.fsf@moondust.localdomain> (raw)
In-Reply-To: <83a7r7ndw7.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 04 Jul 2018 19:50:48 +0300")
At 19:50 +0300 on Wednesday 2018-07-04, Eli Zaretskii wrote:
>
>> From: nljlistbox2@gmail.com (N. Jackson)
>> Date: Mon, 02 Jul 2018 20:19:24 -0400
>>
>> I haven't used the emacs-26 branch since 26.1 was released so
>> I cannot answer your question directly.
>
> Is it possible for you to try the branch? I think it's
> important to know whether this problem still exists on the
> release branch.
Certainly. I have just built the emacs-26 branch [1] and I will
use it as my every-day Emacs from now on.
I'm not sure if we'll learn anything though, given that I've
only seen the problem once in 26.1 which I have been running
almost since the day it was announced. But if I do see it again
I will report back of course.
OT: Are the "potential null pointer dereference" warnings
normal? I don't think I've noticed those before today's build.
For example:
In file included from keyboard.c:25:0:
keyboard.c: In function ‘reorder_modifiers’:
lisp.h:377:40: warning: potential null pointer dereference [-Wnull-dereference]
#define lisp_h_XCDR(c) XCONS (c)->u.s.u.cdr
~~~~~~~~~~~~~~~~^~
lisp.h:1308:10: note: in expansion of macro ‘lisp_h_XCDR’
return lisp_h_XCDR (c);
^~~~~~~~~~~
lisp.h:376:38: warning: potential null pointer dereference [-Wnull-dereference]
#define lisp_h_XCAR(c) XCONS (c)->u.s.car
~~~~~~~~~~~~~~^~
lisp.h:1302:10: note: in expansion of macro ‘lisp_h_XCAR’
return lisp_h_XCAR (c);
^~~~~~~~~~~
Thanks.
N.
[1] Repository revision: 3bbd4ffc68bcc2b3e003a2179a508b82055ad770
next prev parent reply other threads:[~2018-07-04 18:03 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-25 15:01 bug#28596: 26.0.60; [Gnus] Checking mail is no longer reliable and C-g no longer quits N. Jackson
2017-09-25 17:03 ` N. Jackson
2017-09-25 17:14 ` Noam Postavsky
2017-09-26 14:13 ` N. Jackson
2017-09-29 9:10 ` Eli Zaretskii
2017-09-29 15:20 ` Eric Abrahamsen
2017-09-29 17:27 ` N. Jackson
2017-09-29 20:17 ` Eric Abrahamsen
2017-12-02 17:40 ` Eli Zaretskii
2017-12-04 17:14 ` N. Jackson
2017-12-04 17:56 ` Eli Zaretskii
2017-12-22 13:43 ` Eli Zaretskii
2017-12-27 21:00 ` Lars Ingebrigtsen
[not found] ` <871sjfdaql.fsf_-_@moondust.localdomain>
2017-12-28 12:07 ` bug#28596: 26.0.60; Gnus gets into an ambiguous plugged/unplugged state that prevents retrieval of news Lars Ingebrigtsen
2017-12-28 16:27 ` Eli Zaretskii
2017-12-28 16:29 ` Lars Ingebrigtsen
2017-12-28 17:54 ` Eli Zaretskii
2017-12-28 20:15 ` Lars Ingebrigtsen
2017-12-29 0:14 ` N. Jackson
2018-07-02 17:55 ` Eli Zaretskii
2018-07-03 0:19 ` N. Jackson
2018-07-04 16:50 ` Eli Zaretskii
2018-07-04 18:03 ` N. Jackson [this message]
2018-07-04 18:13 ` N. Jackson
2018-07-04 18:30 ` Eli Zaretskii
2018-07-04 18:38 ` N. Jackson
2018-07-04 18:41 ` Eli Zaretskii
2018-07-12 15:33 ` N. Jackson
2018-07-12 15:45 ` Eli Zaretskii
2019-09-27 15:25 ` Lars Ingebrigtsen
2020-07-19 15:44 ` Lars Ingebrigtsen
2018-07-04 18:30 ` Eli Zaretskii
2017-12-11 17:58 ` bug#28596: " N. Jackson
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=8736wy7uai.fsf@moondust.localdomain \
--to=nljlistbox2@gmail.com \
--cc=28596@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=eric@ericabrahamsen.net \
--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.