-
-
Notifications
You must be signed in to change notification settings - Fork 22
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
Build breaks on i386: Abort trap #218
Comments
I know nothing about FreeBSD. Mainly intended for use with RaspberryPI. |
I have access to an OpenBSD machine where I was able to reproduce the compiler warnings (I usually use macOS), and logged a pull request. Unfortunately I don't have access to any 32-bit x86 machines to reproduce the crash. You may have to try debug it yourself, I wrote up some hints in documents/DEBUG.md. |
When I reproduce the problem on amd64 by cross-compiling to i386 I also get this:
Do you know why would the data segment exceed the limit? Is it explicitly specified somewhere? |
(Sorry if you already know this.) UNIX processes can have various limits. You should be able to see them using the ulimit builtin in your shell, e.g. The other possibility is that we're just exceeding a 32-bit address space. I put the following line at the start of main.c because I think these are the biggest data structures: printf("bigcell %lu heap %lu\n", sizeof(bigcell), sizeof(heap)); On my system it showed heap is 720 Mb and bigcell is 80. This should fit comfortably in 4 Gb. So I think it's your process limits. |
On FreeBSD i386 processes have default RLIMIT_DATA=536,870,912 which probably explains the problem. |
Ah, in that case you should be able to override the limit from your shell before starting eisl (or running make, the limits apply to all subprocesses). Something like |
Ok, thank you for your help! |
eisl-2.62 breaks:
Please also note that clang prints a lot of warnings, some of which might to be serious.
clang-14
FreeBSD 13.1
The text was updated successfully, but these errors were encountered: