Hello, Björn! Thanks for the explanation! I've already lost hope of seeing a reply to that, but you appeared out of nowhere and saved the day. Thank you! Are you saying there was a different (better?) optimizer in the previous Factor releases? What happened to it? 17.01.2018, 22:25, "Björn Lindqvis
Doug and Björn, I'd like to point out the following use case for your consideration, and then you can tell me if the selective zeroing of sensitive memory buffers by the GC makes sense. Some sensitive data is stored in a networked application (let's say, a Web Server with its security certificates)
We actually had a command-line argument to the vm to optionally zero the gc
after collection but we removed the feature somewhere around when we
dropped BSD support. It's probably better than nothing but if they could
read your memory after a gc why not just read it before gc instead?
Doug
On Wed
Factor when run in debug mode actually clears memory. See
bump_allocator.hpp. Unfortunately clearing memory is slow as hell. The time
complexity of copying gc is proportional to the number of surviving
objects. But if you want to clear memory too it becomes proportional to the
total number of alloc
The mov [rip-0x117cfdf], eax instruction is indeed peculiar. It actually is
polling a safe point. When ctrl-c is pressed, the running thread is ordered
to stop as quickly as possible. It can't just halt anywhere but must
continue to execute until it comes to a point where it is safe to halt -- a
sa
You can use the dlsym? word: "func_name" "lib_name" dlsym? For functions in
user32.dll, I think you should use "func_name" f dlsym?
2017-08-23 12:25 GMT+02:00 Alexander Ilin :
>
> 23.08.2017, 05:14, "John Benediktsson" :
> > I'm not aware of any easy method. Maybe some other windows dev can
> com
