22:32:20drmeisterWhat's going on here is that clasp is registering methods and this is a method pointer stored at 0x11f5ce5d0 and it's 16 bytes wide (8 bytes for function pointer??? and 8 bytes for "this" adjustment).
22:32:55drmeisterHmmm, this is C++ ABI stuff - it's not x86-64 ABI - this is not a regular function pointer.
22:33:17drmeisterMaybe method calls do more than I was led to believe.
22:35:05drmeisterAll of these weird method pointers have #b001 in the low bits - I'm wondering if it's some kind of tagging scheme?
22:35:17drmeisterWait wait wait. This must be how virtual functions work.
22:35:40drmeisterI bet you these are tagged offsets into the vtable.
22:37:49drmeisterOf course - how else are they going to do virtual method calls?
22:39:07drmeisterWell - this ain't a problem then. I'll just leave anything with any low bits set alone.
22:39:47drmeisterIn that case then I know how to deal with function/method pointers for this first tentative step.
22:40:17drmeisterThe first tentative step being - can I start up the iclasp-boehmprecise -I -n interpreter, save the image and then start the interpreter back up and load the image and continue.
22:41:02drmeisterIt doesn't deal with any compiled code yet.