issue 1
(segfault when running sieve after 836 primes!) reported by dom.orchard
- Steps to reproduce
1. run the "sieve" program from the "progs" directory
lucid sieve
After 836 primes pLucid segfaults:
output(836) : 6449
output(plucid/bin/lucid: line 7: 23353 Segmentation fault luval $1.i
The segmentation fault comes from the "dumpt" function that prints the
output number (i.e. 836) in evaluator/dump.c line 184. Basically it seems
to be a null pointer and I'm not sure why.
Please use labels and text to provide additional information.
Steps to reproduce
1. run the "sieve" program from the "progs" directory
lucid sieve
After 836 primes pLucid segfaults:
output(836) : 6449
output(plucid/bin/lucid: line 7: 23353 Segmentation fault luval $1.i
The segmentation fault comes from the "dumpt" function that prints the
output number (i.e. 836) in evaluator/dump.c line 184. Basically it seems
to be a null pointer and I'm not sure why.
Please use labels and text to provide additional information.