This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author Michael.Felt
Recipients Michael.Felt, davin
Date 2019-02-20.18:11:00
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Another message that surprises me is:
Warning -- multiprocessing.process._dangling was modified by test_multiprocessing_spawn
  Before: <_weakrefset.WeakSet object at 0x3076e810>
  After:  <_weakrefset.WeakSet object at 0x3076e390>

Normally speaking the address 0x30000000 and higher should be "out of bounds" aka a SEGV - unless special actions are taken to open a memory region above 0x2fffffff - for default AIX memory model.

Just calling malloc(), afaik, does not do automatically create a new memory section (0x0000000-0x0fffffff is reserved for kernel CODE, 0x10000000-0x1fffffff is reserved for application CODE, and 0x20000000-0x2fffffff is .data,.bss, "empty aka not-active", .stack).
The area between .end_bss and .stack is the area that sbrk() provides memory from (for calls to malloc(), e.g.)

In short, is there something I do not know understand about Python object pointers that 0x30000000+ values are actually living in 0x20000000-0x2fffffff space?
Date User Action Args
2019-02-20 18:11:00Michael.Feltsetrecipients: + Michael.Felt, davin
2019-02-20 18:11:00Michael.Feltsetmessageid: <>
2019-02-20 18:11:00Michael.Feltlinkissue35828 messages
2019-02-20 18:11:00Michael.Feltcreate