From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 8229-done@debbugs.gnu.org, eggert@cs.ucla.edu
Subject: bug#8229: bug#8215: bug#8229: possibly uninitialized variable in load_charset
Date: Wed, 02 Jun 2021 15:50:50 +0300 [thread overview]
Message-ID: <83v96wxwet.fsf@gnu.org> (raw)
In-Reply-To: <87o8coelrx.fsf_-_@gnus.org> (message from Lars Ingebrigtsen on Wed, 02 Jun 2021 10:03:14 +0200)
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Date: Wed, 02 Jun 2021 10:03:14 +0200
> Cc: 8211@debbugs.gnu.org, 8229@debbugs.gnu.org, 8215@debbugs.gnu.org
>
> Paul Eggert <eggert@cs.ucla.edu> writes:
>
> > I committed my abovementioned workaround into the
> > Emacs trunk on 2011-03-11 (bzr 103589). I don't
> > consider this a fix, though, so I'm leaving this
> > bug report open.
>
> This was ten years ago:
>
> commit 0ac2c2991c1cba4e3c6e5f7b62c7d61b01d69994
> Author: Paul Eggert <eggert@cs.ucla.edu>
> AuthorDate: Mon Mar 7 16:46:23 2011 -0800
> Commit: Paul Eggert <eggert@cs.ucla.edu>
> CommitDate: Mon Mar 7 16:46:23 2011 -0800
>
> * charset.c (load_charset): Abort instead of using uninitialized var.
>
> The code is still pretty much identical, as far as I can tell. Should
> this report be closed now?
I'm closing it. I think non-unified charsets are rarely if ever used
in Emacs these days, but in any case, we have emacs_abort there, so if
the problem ever rears its ugly head, we will catch it.
prev parent reply other threads:[~2021-06-02 12:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-11 0:24 bug#8229: possibly uninitialized variable in load_charset Paul Eggert
2011-03-23 23:19 ` bug#8229: committed the workaround Paul Eggert
2021-06-02 8:03 ` bug#8215: bug#8229: possibly uninitialized variable in load_charset Lars Ingebrigtsen
2021-06-02 12:50 ` Eli Zaretskii [this message]
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=83v96wxwet.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=8229-done@debbugs.gnu.org \
--cc=eggert@cs.ucla.edu \
--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 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).