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
It may be possible to support incorrectly built bash binaries that are very stable (for example, Apple's).
We could hash the binary, and if it matches a binary we know about it use a pre-generated symbol.map.
Is it worth all the extra complexity to support OS X? On the one hand, this is an Apple bug that they should fix (they built bash incorrectly, a feature that is supposed to work doesn't) - on the other hand, it seems unlikely they'll fix a bug in such an obscure feature for at least a few years.
The text was updated successfully, but these errors were encountered:
Yes, I think using debug symbols will work, will just have to create a bunch of pointers to the symbols we need. It's a bit ugly, and I don't know if many Mac users are interested in this...
That's cute. I'm for it. Seems to be much in the spirit of ctypes.sh ;).
I wonder if instead of changing the code too much, we could just add a bash-compat.c shim that only weakly provides the bash exported symbols and looks them up and proxies the calls if actually invoked?
It may be possible to support incorrectly built bash binaries that are very stable (for example, Apple's).
We could hash the binary, and if it matches a binary we know about it use a pre-generated symbol.map.
Is it worth all the extra complexity to support OS X? On the one hand, this is an Apple bug that they should fix (they built bash incorrectly, a feature that is supposed to work doesn't) - on the other hand, it seems unlikely they'll fix a bug in such an obscure feature for at least a few years.
The text was updated successfully, but these errors were encountered: