You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I tried to work it out myself but I'm not to savvy in C/Python interfacing.
I understand that __sF is an array with pointers to stdout (__sF[1]) and stderr (__sF[2]).
So we should get the __sF array and then cast __sF[n] to the equivalent of &__sF[n] ?
Again, maybe there is a more direct approach.
Cheers.
Elias.
The text was updated successfully, but these errors were encountered:
Looking at openbsd, I can't seem to get an easy way to access what we need without a compilation step, since we need two pieces of info:
location of __sF (easy, same as others), and
sizeof(FILE) to locate __sF[1] etc.
If we had easy access to sizeof(FILE), I think we'd be okay, but I can't figure out how to determine without compiling something. And if we are going to compile anyway, it can be pretty simple with cffi:
Hi guys!
I'm trying to bring Wurlitzer to OpenBSD and the following problem arises:
Currently c_stdout_p and c_stderr_p is defined here:
https://github.com/minrk/wurlitzer/blob/1.0.1/wurlitzer.py#L32
Getting the symbol "stdout" for default and "__stderrp" for Mac OS X.
OpenBSD has neither:
https://github.com/openbsd/src/blob/master/include/stdio.h#L198
I tried to work it out myself but I'm not to savvy in C/Python interfacing.
I understand that __sF is an array with pointers to stdout (__sF[1]) and stderr (__sF[2]).
So we should get the __sF array and then cast __sF[n] to the equivalent of &__sF[n] ?
Again, maybe there is a more direct approach.
Cheers.
Elias.
The text was updated successfully, but these errors were encountered: