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/2000-July/006049.html below:

[Python-Dev] Core dump in garbage collection: _PyGC_Insert???

[Python-Dev] Core dump in garbage collection: _PyGC_Insert??? [Python-Dev] Core dump in garbage collection: _PyGC_Insert???Jeremy Hylton jeremy@beopen.com
Mon, 10 Jul 2000 23:19:32 -0400 (EDT)
>>>>> "NS" == Neil Schemenauer <nascheme@enme.ucalgary.ca> writes:

  NS> On Tue, Jul 11, 2000 at 01:05:10AM +0000, Peter Schneider-Kamp
  NS> wrote:
  >> I wouldn't bet my life on it, but I don't think the GC code is
  >> responsible.

  NS> Its hard to say.  The GC code will probably pick up on a lot of
  NS> problems because it touches many objects.  On the other hand, it
  NS> could be my bug.

My first guess would be something other than the GC.  When I was
working on the string_join fix this afternoon, a couple of my interim
versions had refcount problems that lead to core dumps in the garbage
collector.  The GC catches lots of memory problems because it's
touching all the objects; that doesn't mean its to blame for all those
problems.

Which leads me to ask, Barry, did you run purify on an interpreter
with the latest stringobject.c?

Jeremy





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