Open PaulEJKing opened 8 years ago
Concerning your compile problems: to me using '-ansi' seems wrong, because the Elvis sources are not ISO-C compliant, it's traditional C. Do you use the `configure' script for generating your Makefile? If you have trouble doing this, can you describe what you do and show me the output? Also, which gcc version are you using?
I propose to get a clean build running as mentioned above. If there are still coredumps then, you could probably try to generate a bit more information for tracking down the problem: compile Elvis for debugging, run it in 'valgrind' and send me its output or (if you haven't got access to 'valgrind') 'gdb' (and send me the output of the 'bt' command after the crash)?
MIT uses Ubuntu on their machines, and on their athena machine, I compiled Elvis there and for some time it worked, until about a year ago. There must have been a hardware or distribution upgrade or something. THe current CPU is an Intel(R) Xeon(R) CPU E5-2665 0 @ 2.40GHz, running six cores. (40 gigs of RAM).
Elvis started dumping core after only moving around the file with navigation keys. My compilation flags are: gcc -O2 -ansi -ansi is used because getline() is confused with the one in stdio.h This causes a flurry of warnings (this has always been my experience), so I added a -w flag. The warnings consisted of errors such as this random sampling out of the hundreds received:
and so on.
Running Elvis causes a segfault as stated earlier after a few key movements, which I shall show here:
Hope this helps.
Paul King