-
Notifications
You must be signed in to change notification settings - Fork 60
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
实现 MarshalJSON 接口方法, 不会被执行 #74
Comments
This doesn't seem to happen on my fork eh-steve#6 |
This problem seems to happen because |
you are right, your repo handle the but the function type was visited by |
In my fork thanks to mmap_manager, this isn't possible as code is always laid out within 32-bits of the firstmodule for all platforms/architectures |
@eh-steve |
This wouldn't simplify it very much as you still need to check all existing process mappings to ensure the segment you're claiming isn't used by something else |
I know the replaced pkgpath on go.mod is not dealed on this version. the diffent symbols in txts are only your loader and goloader pacakge import other packages |
No I copied and pasted your implementation of There are lots of differences, mainly around fully qualified symbol package naming, anonymous types and invalid kinds from the use of Elem(). You can review the 2 lists to see the differences. |
on your gived pkujhd_register.txt, the symbols type.sync.RWMutex not found, but i get this symbol run with my master branch. |
Apologies I think I uploaded the wrong file, these should be the right ones: |
@eh-steve , It doesn't seem much different, except for pkgpath If I have a good idea for pkgpath, I will fix it I think the compiler of Golang should have already completed the issue of pkgpath |
Annoyingly the go compiler never has to translate a runtime type name to a fully qualified symbol name using only the pkgpath and the rtype name - the compiler builds the correct symbol names using type information from the typecheck/IR, which we don’t have access to at runtime… |
Thank you for informations, i read source code about type name, we need rewrite type name as you said |
I think my implementation is correct as I’ve included a panic if the loader’s type is identical but the symbol name doesn’t match, and stopped seeing panics eventually |
go1.19 AMD64
loader 执行将输出 “{}” 而不是 "1"
The text was updated successfully, but these errors were encountered: