Your message dated Sat, 26 Aug 2023 10:50:15 +0000
with message-id <[email protected]>
and subject line Bug#1039474: fixed in ghc 9.4.6-1
has caused the Debian Bug report #1039474,
regarding ghc: GHCi sometimes segfaults
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 [email protected]
immediately.)


-- 
1039474: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039474
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: ghc
Version: 9.0.2-4
Severity: normal
Tags: upstream
X-Debbugs-Cc: [email protected]

Dear Maintainer,

GHCi seems to segfault randomly every now and then, after seemingly
failing to allocate memory for simple operations, e.g.:

 $ ghci                         
 GHCi, version 9.0.2: https://www.haskell.org/ghc/  :? for help
 ghci> 750+850
 1600
 ghc: mmap 4096 bytes at (nil): Cannot allocate memory
 ghc: Try specifying an address with +RTS -xm<addr> -RTS
 zsh: segmentation fault  ghci

Shortly afterwards, the same commands may work perfectly well. I've
observed this happen on two completely different machines, but have
been unable to consistently reproduce.

Upstream describes the issue at

 
https://discourse.haskell.org/t/facing-mmap-4096-bytes-at-nil-cannot-allocate-memory-youre-not-alone/6259

but it seems that the fix has not been backported to 9.0.x. I have no
idea how hard it would be to do.

Sorry for not catching this before Bookworm released. I do believe I
saw the segfault once or twice before the release, but I must have
chalked it up to a hardware fault or something :-/


-- System Information:
Debian Release: 12.0
  APT prefers stable-security
  APT policy: (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.1.0-9-amd64 (SMP w/6 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages ghc depends on:
ii  dpkg            1.21.22
ii  gcc             4:12.2.0-3
ii  libbsd-dev      0.11.7-2
ii  libc6           2.36-9
ii  libc6-dev       2.36-9
ii  libffi-dev      3.4.4-1
ii  libffi8         3.4.4-1
ii  libgmp-dev      2:6.2.1+dfsg1-1.1
ii  libgmp10        2:6.2.1+dfsg1-1.1
ii  libncurses-dev  6.4-4
ii  libtinfo6       6.4-4

ghc recommends no packages.

Versions of packages ghc suggests:
pn  ghc-doc      <none>
pn  ghc-prof     <none>
pn  haskell-doc  <none>
ii  llvm-13      1:13.0.1-11+b2
ii  perl         5.36.0-7

-- no debconf information

Attachment: signature.asc
Description: PGP signature


--- End Message ---
--- Begin Message ---
Source: ghc
Source-Version: 9.4.6-1
Done: Ilias Tsitsimpis <[email protected]>

We believe that the bug you reported is fixed in the latest version of
ghc, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ilias Tsitsimpis <[email protected]> (supplier of updated ghc package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Fri, 25 Aug 2023 20:12:47 +0300
Source: ghc
Architecture: source
Version: 9.4.6-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Haskell Group 
<[email protected]>
Changed-By: Ilias Tsitsimpis <[email protected]>
Closes: 1017663 1039474
Changes:
 ghc (9.4.6-1) unstable; urgency=medium
 .
   * Upload to unstable (Closes: #1017663, #1039474)
Checksums-Sha1:
 3d49cfc2d4764fb37c9cd8c73016e4b99ace2ae1 2626 ghc_9.4.6-1.dsc
 6d6fa1fb99a7718a26c37bff2a1edaec4dfd86a9 56488 ghc_9.4.6-1.debian.tar.xz
 d1c0b733ca0ed77e7a7f453c6d64f92b83bf375a 13090 ghc_9.4.6-1_amd64.buildinfo
Checksums-Sha256:
 83e4d05fd9838636f98a1d1ba106cca772b7471ab7efe0c5f0d55247edefb509 2626 
ghc_9.4.6-1.dsc
 8492a665b6c411afd7cda41cbf713b931e0caee2a7f696b0ed7ea4487d0e4acc 56488 
ghc_9.4.6-1.debian.tar.xz
 75476a3632456d6808f0ff7dbc7cb52902a454ca9f0c46d0cc90d4e0387b3916 13090 
ghc_9.4.6-1_amd64.buildinfo
Files:
 8c4fd1416dc8293334c4fad857e62eda 2626 haskell optional ghc_9.4.6-1.dsc
 4f811a2b1155f888c46390f55e85a993 56488 haskell optional 
ghc_9.4.6-1.debian.tar.xz
 5149361962d1da82642e58e3d684e253 13090 haskell optional 
ghc_9.4.6-1_amd64.buildinfo

-----BEGIN PGP SIGNATURE-----

iQJIBAEBCgAyFiEEJ9c8pfW11+AaUTb116hngMxkQDwFAmTp1fkUHGlsaWFzdHNp
QGRlYmlhbi5vcmcACgkQ16hngMxkQDy35RAAk1MGECTA9BfNFqpDV5jJ4CIAZpnf
IXJTmgcoc1BDTCAfKpu2NMMJY83GSWXr06rmgNaxDxFCtPYochBkZfbR+hwBPfMj
W1PQJ76ciVvJnvLflJhNmAfSHtmy9YYVXwPS3OVQNkD0hkKnVKOYDi/XmChkl6Di
s9vbDpW0ND8tWKORPi9s9wpN3sBZYKE33yMpoGX433TZat9GXKS08LVA81GdxXTm
6vT6Rbxp9P+qhmE1Mzj+eTfhZEZUONqgGbcQf2IIbA43PvJewKqAFxsymQYYTcSo
Bwb/GjYMHlEvnKbCkZ466Y6JPxBK/gMxj4/wsbDUt6ePROvpaQFMdPo7YRU1u/ex
tio4kk0tAph/Bjb3EJhjLwaMm+6e2uBe744VNg9x5S5mIgyddIjn2WOGqsbd7L8x
+LdQVUMNQtfoefO1wwJnhLvcH1p0PbDlGLP6UNaCvbPVIxoVHs7lmWLKMSTGgdx+
7LYkQ5S9W9QcPdGi3BF7AvI2/5zWQhYgWgJ4Vs0yA1mc5aLgFjajpztjlMbED6ci
06fqEYQv0F/6pVPG6YBt6+CDk3Lf2CQws2O5M/2WlH/woQmSPHwKLqyTgqL5mGSI
sfsnabIQ11TUB2eAehUPqWidwj87Aa8aJBOYnDrs3kHbB03r+f6uNxe/KHCipeK+
HW3LOyGUoulgIbU=
=h5KZ
-----END PGP SIGNATURE-----

--- End Message ---
_______________________________________________
Pkg-haskell-maintainers mailing list
[email protected]
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-haskell-maintainers

Reply via email to