libera/#sicl - IRC Chatlog
Search
2:19:45
moon-child
obviously, it is a safety problem to be able to turn an integer into a pointer. Is it a problem to be able to go the other way?
2:21:34
moon-child
I suppose it could be used to aid in exploiting other vulnerabilities. But while I can not see any problem with it per se, I also can not think of any reason why it would be useful to interpret the address of an object as an integer, unless debugging a gc
2:23:07
moon-child
many implementations will print an unreadable object using its address by default. But this seems suspect to me. An object could move to a different address; an object could be reclaimed, and another could be given the same address; addresses are not very distinctive, and a human may not immediately be able to tell the difference between two similar-looking addresses
2:23:39
moon-child
a display of slots, while somewhat unprincipled, would be no _less_ unprincipled due to the above problems, and probably more useful
2:25:48
hayley
I heard Java prints the identity hash code by default, which is stable regardless of GC.
3:35:58
Bike
displaying the pointer is pretty convenient practically speaking, and not as verbose as dumping slots
4:05:40
Bike
might be nice if you could kind of reverse hash it into something more human readable arbitrary text