How can I filter unwanted unwanted types(not in my code) from DIA SDK?
-
Hello, I am using DIA SDK for extracting user defined complex types(just I used in my C++ code). I don't know all my types(used in code) before extracting from DIA SDK with names and members(data members& functions). It shows everything, I mean all those user defined types which I don't need at all(i.e kernel types and enums & structs). I only want to enumerate those which are strictly used in my code(i.e in Dll/EXE in any format). Is there is any way out at all by which we can restrict those unwanted (Kernel source types or MSFT specific source code) types to appear? Regards Usman
-
Hello, I am using DIA SDK for extracting user defined complex types(just I used in my C++ code). I don't know all my types(used in code) before extracting from DIA SDK with names and members(data members& functions). It shows everything, I mean all those user defined types which I don't need at all(i.e kernel types and enums & structs). I only want to enumerate those which are strictly used in my code(i.e in Dll/EXE in any format). Is there is any way out at all by which we can restrict those unwanted (Kernel source types or MSFT specific source code) types to appear? Regards Usman
-
glitteringsound wrote:
It shows everything
What does this mean, what is it that does the showing? You need to explain your problem a bit better if you want a suggestion to help you.
Just say 'NO' to evaluated arguments for diadic functions! Ash
I statted completely.. Rephrasing..It shows every user defined type that's not used or declare inside my code. I mean If I have declared and use "MyClass" as class in my dll/exe then it should enumerate only this. It enumerates all those UDTs(User Defined Types)which 's not used or declared in my binary(dll/exe).Those comes from kernel modules and libraries. As we know that every program implicitely linked with some kernel imports(i.e kernel32.lib,user32.lib, gdi32.lib, winspool.lib ,comdlg32.lib....). I only need strictly those user defined types those I declared inside my source code.For this I can give or hardcode that user defined type to which I want to enumerate. But this is not the solution of the problem. Some I don't know earlier the name of type used in my source code. In that case I need list of all of those types which I used or declared in my source code.
-
I statted completely.. Rephrasing..It shows every user defined type that's not used or declare inside my code. I mean If I have declared and use "MyClass" as class in my dll/exe then it should enumerate only this. It enumerates all those UDTs(User Defined Types)which 's not used or declared in my binary(dll/exe).Those comes from kernel modules and libraries. As we know that every program implicitely linked with some kernel imports(i.e kernel32.lib,user32.lib, gdi32.lib, winspool.lib ,comdlg32.lib....). I only need strictly those user defined types those I declared inside my source code.For this I can give or hardcode that user defined type to which I want to enumerate. But this is not the solution of the problem. Some I don't know earlier the name of type used in my source code. In that case I need list of all of those types which I used or declared in my source code.
glitteringsound wrote:
It shows every user defined type
Once again what do you mean by 'It' here. What exactly are you doing (or is something else doing) that shows whatever it is that you do not want to see. You also mention enumeration, again who or what is doing the enumerating and what are they enumerating. Sorry but I am very confused.
Just say 'NO' to evaluated arguments for diadic functions! Ash
-
glitteringsound wrote:
It shows every user defined type
Once again what do you mean by 'It' here. What exactly are you doing (or is something else doing) that shows whatever it is that you do not want to see. You also mention enumeration, again who or what is doing the enumerating and what are they enumerating. Sorry but I am very confused.
Just say 'NO' to evaluated arguments for diadic functions! Ash
DIA SDK is the API available by Microsoft under C:\Program Files\Microsoft Visual Studio 10.0\DIA SDK\... It always gives you the debugging information 2 or 3 times more than that of Dbghelp and DbgEng etc. It enumerates pdbs and allows the users to extract information like 1 - Types(names) & base class details. 2 - Members(Their names and full signature details, parameter offsets and methods RVA) 3 - Type data members. and lot more what ever you required. My problem is that yes I want to enumerate all these things. But basically my problem is that I don't want the details(which I mentioned above ) of all those types which are not defined in my code.What It does now , it starts from kernel modules (Dll's) , enumerates the details(i.e types , method associated with that type and so on..) and trail down to the end of the user defined types(classes',structs and enums). I only want my types (which are strictly defined in my code) to be enlist. I don't want all kernel related types.i.e contained inside (MSCVP100.dll,KERNEL32.dll,User32.dll,Ole32.dll,OleAut32.dll). If still any confusion is there let me know then..
-
DIA SDK is the API available by Microsoft under C:\Program Files\Microsoft Visual Studio 10.0\DIA SDK\... It always gives you the debugging information 2 or 3 times more than that of Dbghelp and DbgEng etc. It enumerates pdbs and allows the users to extract information like 1 - Types(names) & base class details. 2 - Members(Their names and full signature details, parameter offsets and methods RVA) 3 - Type data members. and lot more what ever you required. My problem is that yes I want to enumerate all these things. But basically my problem is that I don't want the details(which I mentioned above ) of all those types which are not defined in my code.What It does now , it starts from kernel modules (Dll's) , enumerates the details(i.e types , method associated with that type and so on..) and trail down to the end of the user defined types(classes',structs and enums). I only want my types (which are strictly defined in my code) to be enlist. I don't want all kernel related types.i.e contained inside (MSCVP100.dll,KERNEL32.dll,User32.dll,Ole32.dll,OleAut32.dll). If still any confusion is there let me know then..
I have not used DIA but looking at the documentation there does not seem to be an obvious solution to your problem. I suspect part of the problem is the extra information that is added to the PDB when you include a header file that defines Windows functions; everything is included in the PDB even if it is not directly referenced in the final .exe file. There seem to be lots of pointers in the section on Symbols and Symbol Tags but no direct suggestion relevant to your question. Since this is a rather specialised subject you may be better trying one of the Microsoft forums that deal with the subject.
Just say 'NO' to evaluated arguments for diadic functions! Ash