os.write segfaults
Sup, folks!) I have yet another question on SO, bump it here. https://stackoverflow.com/questions/44649591/rpython-segfaults-on-os-write -- Kind regards, Aleksandr Koshkin.
It seams that the problem lies in default GC (minimark), for some reason it frees memory a bit in advance. By setting --gc=ref it runs correctly. Is it a bug? 2017-06-20 13:35 GMT+03:00 Aleksandr Koshkin <tinysnippets@gmail.com>:
Sup, folks!) I have yet another question on SO, bump it here. https://stackoverflow.com/questions/44649591/rpython-segfaults-on-os-write
-- Kind regards, Aleksandr Koshkin.
-- Kind regards, Aleksandr Koshkin.
Hi, On 20 June 2017 at 12:35, Aleksandr Koshkin <tinysnippets@gmail.com> wrote:
I have yet another question on SO, bump it here. https://stackoverflow.com/questions/44649591/rpython-segfaults-on-os-write
The library is supposed to be initialized first. I think you need to call rpython_startup_code() first to do that. A bientôt, Armin.
participants (2)
-
Aleksandr Koshkin -
Armin Rigo