bug-gnu-pspp
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: PSPP-BUG: Bug Report for PSPP 0.7.8 on Fedora


From: Ben Pfaff
Subject: Re: PSPP-BUG: Bug Report for PSPP 0.7.8 on Fedora
Date: Wed, 07 Mar 2012 22:19:13 -0800
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/23.2 (gnu/linux)

Eliana <address@hidden> writes:

> Sorry, I did not know you needed that, I was just following the
> instructions in the output   It was so far above the instructions and
> error listing , I did not even see it, but just reran on a smaller
> sample so I can provide that to you.

Ordinarily, full output would not be necessary, but I was not
able to reproduce the problem so it seemed like a good question
to ask.

> Note that the complaints pspp made about inappropriate data were due
> to my not yet having figured out where in the first line of code to
> put /FIRSTCASE=2.  I have now got that working but the program I reran
> to provide you with output, I left without the firstcase statement as
> in the original run.

That makes sense.

> Before I paste that long output here, let me mention that after
> getting John's response to a different query on  pspp-help, I revised
> the program in two ways and got it to run successfully, so I think the
> issue may just be it had no error message to catch my error?
>
> I am new and believed the manual when it said blank lines could be
> used to finish a command.    Once I added a period at the end of the
> last line, it ran smoothly.

Indeed, a blank line should terminate a command.  If it doesn't,
then this sounds like a bug in PSPP.  To check, I tried writing a
syntax file a few ways with blank lines (and no period) at the
end.  The cases that I tried worked as I expected: the last
command in the file was executed.  Can you pass along an example
that doesn't work?  I would like to fix the problem.

> I will attach the program file I used to recreate the scenario.

Hmm.  I still cannot reproduce the crash.  I guess that it is
possible that the bug has already been fixed, seeing as 0.7.8 is
slightly old.

Thank you for the report and the additional information.
-- 
Ben Pfaff 
http://benpfaff.org



reply via email to

[Prev in Thread] Current Thread [Next in Thread]