-
Notifications
You must be signed in to change notification settings - Fork 57
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
OpenBSD port #87
Comments
Passing a pointer to heap memory to
but I still don't understand why it can't write directly to the data segment. |
wow, cool that it works! I'm not really sure why it's failing, the code seems okay to me... I think there's no guarantee about what order constructors are run in, so maybe they're being run too early, and OpenBSD expects some other constructor to run first? These might not really be necessary anymore though... I might be able to refactor them out. I think now terminal settings are better handled, so less cleanup is necessary. (Sorry for the slow response to PRs, I'll get to them!) |
Although it passes the workaround, it proceeds to segfault here:
|
After rebuilding the symbol undefine list for OpenBSD (using the Linux list as the starting point), the "Bad address" Program still segfaults in |
Project now builds using the feature branch from #86
It segfaults at runtime in
init_terminal_settings
inwrappers.c
, whenioctl(2)
(called bytcgetattr(3)
) attempts to write to this memory location:ioctl(2)
fails witherrno == 14
(EFAULT, "Bad address").Is it possible that there is some unsafe programming practice at play here that OpenBSD catches?
The text was updated successfully, but these errors were encountered: