-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Running out of PSP #5
Comments
The message is printed by |
With increases info level, the error looks like
|
I've rebuilt cohomolo with gcc 5.2.0 installed using Homebrew and the problem disappeared. I will now update my PR #1 with another example. This show how testing is important ! |
Thank you to Derek who explained this to me today: The cohomolo package consists of a large number of separate C programs, most of which define (their own value of) PSP. To find out exactly which C program was running when the crash occurred, edit
at the beginning of that file. Then it should print out each program call before running it. |
Resolved for now - the remedy is to used gcc instead of clang on OS X. Similar problems known for KBMAG. It may have sense to get to the original problem and make it working with clang - I've filed #6 to remind of that. |
I am not sure why this was closed and a new issue was opened -- this issue is not resolved, as it still occurs; we merely discovered that it depends on the compiler whether the failure appears or not... Since #6 contains far less details (e.g. no information on what the failure is, how to track down which of the many executables triggers it ec.), I have reopened this issue and closed #6. |
ok - maybe #6 should be deleted in this case... |
I don't think you can delete issues, just close them |
I've added PR #1 adding a test file based on the first of the two examples from
testdata/test.g
. The 2nd example from there fails withOut of space.Increase PSP.
error - I don't know where to set it as many source filed have# define PSP
lines with different values of PSP.The text was updated successfully, but these errors were encountered: