A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2013-March/124502.html below:

[Python-Dev] Disabling string interning for null and single-char causes segfaults

[Python-Dev] Disabling string interning for null and single-char causes segfaults [Python-Dev] Disabling string interning for null and single-char causes segfaultsAntoine Pitrou solipsis at pitrou.net
Sat Mar 2 16:31:36 CET 2013
On Fri, 1 Mar 2013 16:24:42 +0100
Stefan Bucur <stefan.bucur at gmail.com> wrote:
> 
> However, after applying this modification, when running "make test" I get a
> segfault in the test___all__ test case.
> 
> Before digging deeper into the issue, I wanted to ask here if there are any
> implicit assumptions about string identity and interning throughout the
> interpreter implementation. For instance, are two single-char strings
> having the same content supposed to be identical objects?

From a language POV, no, but inside a specific interpreter such as
CPython it may be a reasonable expectation.

> I'm assuming that it's either this, or some refcount bug in the interpreter
> that manifests only when certain strings are no longer interned and thus
> have a higher chance to get low refcount values.

Indeed, if it's a real bug it would be nice to get it fixed :-)

Regards

Antoine.


More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4