How to remove all source code symbol names from Release build
-
Hi All, My goal is to remove all references to product A from product B executable. When searching for A product name in B product executable I've found the following constructs ЂР[ .?AV?$Composite@I@@ or in hex 80 D0 5B 00 00 00 00 00 2E 3F 41 56 3F 24 43 6F 6D 70 6F 73 69 74 65 40 49 40 40 in PE executable's .data section. Looks like all the class names from source code are mentioned there. I'm reusing source code from product A so its name heavily mentioned in these "symbols". Note, that I'm looking at release build, with no debug info. Could someone please suggest what those constructs are and how to avoid them? WBR O.Z.
-
Hi All, My goal is to remove all references to product A from product B executable. When searching for A product name in B product executable I've found the following constructs ЂР[ .?AV?$Composite@I@@ or in hex 80 D0 5B 00 00 00 00 00 2E 3F 41 56 3F 24 43 6F 6D 70 6F 73 69 74 65 40 49 40 40 in PE executable's .data section. Looks like all the class names from source code are mentioned there. I'm reusing source code from product A so its name heavily mentioned in these "symbols". Note, that I'm looking at release build, with no debug info. Could someone please suggest what those constructs are and how to avoid them? WBR O.Z.
:confused: why ? Are you afraid someone might look at your product B and find that you did nothing but use product A ? If you bought library A and use in your product B and try to hide that, people who worked on A might be a little pissed off. no ?
Maximilien Lincourt Your Head A Splode - Strong Bad
-
:confused: why ? Are you afraid someone might look at your product B and find that you did nothing but use product A ? If you bought library A and use in your product B and try to hide that, people who worked on A might be a little pissed off. no ?
Maximilien Lincourt Your Head A Splode - Strong Bad
Don't worry :) both A and B belong to us and no pissed off people around, for now at least :). This is just a matter of business decisions. Of course I can use executable compression for obfuscation purposes but I would like to find out what the problem actually is anyway.
-
Don't worry :) both A and B belong to us and no pissed off people around, for now at least :). This is just a matter of business decisions. Of course I can use executable compression for obfuscation purposes but I would like to find out what the problem actually is anyway.