From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Marko Rauhamaa Newsgroups: gmane.lisp.guile.user Subject: Re: Guile bugs Date: Sun, 10 Sep 2017 01:31:08 +0300 Message-ID: <87wp57mrmb.fsf@elektro.pacujo.net> References: <87lgtajpkc.fsf@web.de> <87h8y7ruuz.fsf_-_@gnu.org> <877ez384eu.fsf@elektro.pacujo.net> <87k2333qx9.fsf@gmail.com> <87pocvc5ya.fsf@elektro.pacujo.net> <87poculu2v.fsf@gnu.org> <87inimd9yy.fsf@elektro.pacujo.net> <87k232cu3p.fsf@netris.org> <877ez2co3j.fsf@elektro.pacujo.net> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: blaine.gmane.org 1504996321 11867 195.159.176.226 (9 Sep 2017 22:32:01 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Sat, 9 Sep 2017 22:32:01 +0000 (UTC) User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.1 (gnu/linux) Cc: Ludovic =?utf-8?Q?Court=C3=A8s?= , Guile User To: Linas Vepstas Original-X-From: guile-user-bounces+guile-user=m.gmane.org@gnu.org Sun Sep 10 00:31:51 2017 Return-path: Envelope-to: guile-user@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dqoHj-0001k6-WA for guile-user@m.gmane.org; Sun, 10 Sep 2017 00:31:32 +0200 Original-Received: from localhost ([::1]:51054 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dqoHr-0006uz-6q for guile-user@m.gmane.org; Sat, 09 Sep 2017 18:31:39 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:35403) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dqoHR-0006ua-8c for guile-user@gnu.org; Sat, 09 Sep 2017 18:31:14 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dqoHQ-0002DS-8p for guile-user@gnu.org; Sat, 09 Sep 2017 18:31:13 -0400 Original-Received: from [2001:1bc8:1a0:5384:7a2b:cbff:fe9f:e508] (port=42702 helo=pacujo.net) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dqoHQ-0002Af-0G; Sat, 09 Sep 2017 18:31:12 -0400 Original-Received: from elektro.pacujo.net (192.168.1.200) by elektro.pacujo.net; Sun, 10 Sep 2017 01:31:08 +0300 Original-Received: by elektro.pacujo.net (sSMTP sendmail emulation); Sun, 10 Sep 2017 01:31:08 +0300 In-Reply-To: (Linas Vepstas's message of "Sat, 9 Sep 2017 16:14:37 -0500") X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 2001:1bc8:1a0:5384:7a2b:cbff:fe9f:e508 X-BeenThere: guile-user@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: General Guile related discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guile-user-bounces+guile-user=m.gmane.org@gnu.org Original-Sender: "guile-user" Xref: news.gmane.org gmane.lisp.guile.user:14103 Archived-At: Linas Vepstas : > So if you used GC_malloc_atomic() in your code, then gc will NOT scan > that region for pointers. guile-2.2 does this correctly for strings (I > checked) because strings will never contain pointers. I have not > checked other uses. The question about mmap(2) is addressed more directly by the README under : Any objects not intended to be collected must be pointed to either from other such accessible objects, or from the registers, stack, data, or statically allocated bss segments. [...] WARNING: pointers inside memory allocated by the standard malloc are not seen by the garbage collector. Thus objects pointed to only from such a region may be prematurely deallocated. It is thus suggested that the standard malloc be used only for memory regions, such as I/O buffers, that are guaranteed not to contain pointers to garbage collectible memory. [...] WARNING: the collector does not guarantee to scan thread-local storage (e.g. of the kind accessed with pthread_getspecific). The collector does scan thread stacks Now, the question is, can you make your multigigabyte allocation go into these excluded memory segments? Are you still hit by the pathological GC behavior you reported? Marko