> I note your original report shows a version of 0.4.0-7+b1. I don't > recognize the "+b1" - what does that signify?
No idea. That's more .deb packaging detail than I know. > I also see you're running a 64 bit system, whereas I have a 32 bit > system, and I suspect that's the real problem. Likely so, though I have a coworker who has pspp working sans segfault under OSX. He's not around, though, so I can't ask whether the ports tree compiles it as 64- or 32-bit. I can confirm that it segfaults both on a CentOS/AMD64 box in the office, and on a remote box (Ubuntu/EM64, maybe). > Would you mind dumping > a core file and using gdb to find out where the segfault was? The 64-bit CentOS box on which pspp was compiled by hand gives this: (gdb) run myfile.syn Starting program: /usr/local/bin/pspp myfile.syn Program received signal SIGSEGV, Segmentation fault. 0x000000000043e4b6 in dict_get_vars (d=0x5d2270, vars=0x5cf248, cnt=0x5cf244, exclude_classes=6) at dictionary.c:247 247 (*vars)[(*cnt)++] = d->var[i]; Hope that helps, A
