-
Enhancement
-
Resolution: Won't Fix
-
P4
-
6
-
x86
-
windows
On Windows builds, not all private symbols are exported.
make/windows/build_vm_def.sh generates vm.def file for the list of function symbols to be exported. It appears to only pick symbols with signature "??_7.*@@6B@", which, according to this wiki (http://en.wikipedia.org/wiki/Microsoft_Visual_C%2B%2B_Name_Mangling#Encoded_Number), they are 'vftable's functions, the rest symbols are not exported.
Missing symbols will result inaccurate callsite.
The logic is dated back to 1.5.
make/windows/build_vm_def.sh generates vm.def file for the list of function symbols to be exported. It appears to only pick symbols with signature "??_7.*@@6B@", which, according to this wiki (http://en.wikipedia.org/wiki/Microsoft_Visual_C%2B%2B_Name_Mangling#Encoded_Number), they are 'vftable's functions, the rest symbols are not exported.
Missing symbols will result inaccurate callsite.
The logic is dated back to 1.5.
- relates to
-
JDK-6995781 RFE: Native Memory Tracking (Phase 1)
-
- Closed
-
-
JDK-7152671 RFE: Windows decoder should add some std dirs to the symbol search path
-
- Closed
-