-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Use of MA_RESERVED1 breaks on recent Solaris builds #1002
Comments
What are you talking about? lol |
|
Oh I get it now. Yeah, I think you can freely remove both "R" and "*". I don't remember where I got that from. |
MA_RESERVED1 never meant anything, and the macro is going away in the next release of Solaris. MA_NORESERVE wasn't really mapped to anything useful, either. Removing the use of both macros shouldn't make any material difference, and will be compatible across more versions of Solaris. Fixes giampaolo#1002.
This is against internal-to-Oracle Solaris, but recently
MA_RESERVED1
was renamed toMA_CORE_NODATA
, as that value was given a specific use. Currently, psutil translates that flag to*
, but I can't find any documentation on what that's supposed to mean. The documentation for the perms field in /proc/pid/maps in proc(5) only talks aboutr
,w
,x
,s
, andp
, and notR
and*
as are also used in_psutil_sunos.c
. SinceMA_RESERVED1
was never used for anything (at least, not in recent memory), it's not clear that the*
meant anything either, and it probably should just be dropped. I can whip up a pull request for that, if desired.The text was updated successfully, but these errors were encountered: