[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#691709: marked as done (gccgo: Concurrent pi example runs out of memory)

Your message dated Wed, 08 May 2013 14:53:03 +0200
with message-id <518A4AAF.2050202@debian.org>
and subject line Re: Bug#691709: gccgo: Concurrent pi example runs out of memory
has caused the Debian Bug report #691709,
regarding gccgo: Concurrent pi example runs out of memory
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
691709: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=691709
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: gccgo-4.7
Version: 4.7.2-4
Severity: normal

Dear Maintainer,

Compiling and running the "concurrent pi" example from golang.org under
PowerPC results in the following error (cpi.go below contains concurrent pi
example code):

----
$ gccgo-4.7 cpi.go 
~
$ ./a.out 
runtime: memory allocated by OS (0x9ff57000) not in usable range [0x20100000,0xa0100000)
runtime: out of memory: cannot allocate 2097152-byte block (1739587584 in use)
throw: out of memory

goroutine 1 [running]:

goroutine 2 [syscall]:
no stack trace available

goroutine 3 [runnable]:
panic during panic
$ echo $?
3
----

This doesn't happen with the same version of gccgo under x86_64.  The host has
1+ GiB RAM + 2 GiB swap (mostly free) so I don't think it's an actual memory
shortage.  Nonetheless, lowering the number of spawned goroutines to 825 makes
the program run (> 825 crashes it, all regardless of free system memory).

Thanks!

-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: powerpc (ppc)

Kernel: Linux 3.2.0-4-powerpc
Locale: LANG=ca_ES.UTF-8, LC_CTYPE=ca_ES.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages gccgo-4.7 depends on:
ii  gcc-4.7       4.7.2-4
ii  gcc-4.7-base  4.7.2-4
ii  libc6         2.13-35
ii  libc6-dev     2.13-35
ii  libgmp10      2:5.0.5+dfsg-2
ii  libgo0        4.7.2-4
ii  libmpc2       0.9-4
ii  libmpfr4      3.1.0-5
ii  zlib1g        1:1.2.7.dfsg-13

gccgo-4.7 recommends no packages.

Versions of packages gccgo-4.7 suggests:
ii  gccgo-4.7-doc  4.7.2-1
ii  libgo0-dbg     4.7.2-4

-- no debconf information

--- End Message ---
--- Begin Message --- 
Am 27.11.2012 10:31, schrieb Ivan Vilata i Balaguer:
> Matthias Klose (2012-11-27 08:25:37 +0100) wrote:
> 
>> - please recheck with 4.7 in experimental
>> - please check with explicitly using gold
>> - please check with 4.8/snapshot
>>
>> If the problem persists, maybe file an upstream report.
> 
> I tested with 4.7.11 in experimental and the problem persists.
> 
> However I don't have the time to test the other suggestions on this
> computer, so you can close the bug if you want.

doing so.

--- End Message ---
Reply to: