From: Andreas Schwab <schwab@suse.de>
To: Jason Rumney <jasonr@gnu.org>
Cc: bug-gnu-emacs@gnu.org, 38@emacsbugs.donarmstrong.com,
"Göran Uddeborg" <goeran@uddeborg.se>
Subject: Re: No coding system used for environment variables
Date: Wed, 05 Mar 2008 11:34:53 +0100 [thread overview]
Message-ID: <jed4q9sble.fsf@sykes.suse.de> (raw)
In-Reply-To: <47CE607B.1000708@gnu.org> (Jason Rumney's message of "Wed\, 05 Mar 2008 08\:57\:31 +0000")
Jason Rumney <jasonr@gnu.org> writes:
> YAMAMOTO Mitsuharu wrote:
>> Second, as DECODE_FILE causes GC and string compaction in general,
>> some variables such as `nm' in Fexpand_file_name may not point to
>> valid data after that.
>
> This is a problem on some systems that still do not support stack marking
> for GC protection of such variables. But I think this bug is important
> enough to fix those problems rather than revert the patch.
Only Lisp_Object variables are protected. Failing to protect
non-Lisp_Object pointers can result in crashes. A crash is always the
worst possible problem.
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2008-03-05 10:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-21 21:40 No coding system used for environment variables Göran Uddeborg
2008-03-05 0:40 ` Jason Rumney
2008-03-05 2:22 ` YAMAMOTO Mitsuharu
2008-03-05 8:57 ` Jason Rumney
2008-03-05 9:16 ` YAMAMOTO Mitsuharu
2008-03-05 10:11 ` Jason Rumney
2008-03-05 11:00 ` YAMAMOTO Mitsuharu
2008-03-05 10:34 ` Andreas Schwab [this message]
2008-03-05 16:25 ` Stefan Monnier
2008-03-07 12:12 ` YAMAMOTO Mitsuharu
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=jed4q9sble.fsf@sykes.suse.de \
--to=schwab@suse.de \
--cc=38@emacsbugs.donarmstrong.com \
--cc=bug-gnu-emacs@gnu.org \
--cc=goeran@uddeborg.se \
--cc=jasonr@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).