Package: nqc
Version: 3.1.r6-1
Running nqc with -TSwan -L segfaults. Here is a demonstration:
% cat web2.nqc
task main()
{
}
% valgrind nqc -TSwan -L web2.nqc
==26607== Memcheck, a memory error detector
==26607== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al.
==26607== Using Valgrind-3.12.0 and LibVEX; rerun with -h for copyright info
==26607== Command: nqc -TSwan -L web2.nqc
==26607==
==26607==
==26607== Process terminating with default action of signal 11 (SIGSEGV)
==26607== Bad permissions for mapped region at address 0x43D4E0
==26607== at 0x41BC6D: ??? (in /usr/bin/nqc)
==26607== by 0x41BEB5: ??? (in /usr/bin/nqc)
==26607== by 0x41F375: ??? (in /usr/bin/nqc)
==26607== by 0x404259: ??? (in /usr/bin/nqc)
==26607== by 0x402275: ??? (in /usr/bin/nqc)
==26607== by 0x56F42B0: (below main) (libc-start.c:291)
==26607==
==26607== HEAP SUMMARY:
==26607== in use at exit: 229,107 bytes in 4,197 blocks
==26607== total heap usage: 5,845 allocs, 1,648 frees, 427,541 bytes allocated
==26607==
==26607== LEAK SUMMARY:
==26607== definitely lost: 32 bytes in 1 blocks
==26607== indirectly lost: 27 bytes in 2 blocks
==26607== possibly lost: 65,512 bytes in 2,562 blocks
==26607== still reachable: 163,536 bytes in 1,632 blocks
==26607== suppressed: 0 bytes in 0 blocks
==26607== Rerun with --leak-check=full to see details of leaked memory
==26607==
==26607== For counts of detected and suppressed errors, rerun with: -v
==26607== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
Segmentation fault
%
I came across this problem in Ubuntu,
<URL: https://bugs.launchpad.net/ubuntu/+source/nqc/+bug/436456 >.
--
Happy hacking
Petter Reinholdtsen
