How to import my own dll function names into IDA

[demonguy]

i want TO debug WOW in which my dll is injected by using IDA. Then how can i import my functions' names?

[~Unknown~]

I don't know how to import function names, but is there some reason you just don't use Debugger.Launch Method (System.Diagnostics) ?

[demonguy]

i'm using C++ so .NET won't work

[DarkLinux]

I really dont get what you want to do? You want to debug your dll? If so use VS, it can debug your work even if its injected into wow. If you want to look at your dll with IDA just compile it as debug and the names should kick around. But other than that, I have no idea what you are trying to do lols....

[demonguy]

I really dont get what you want to do? You want to debug your dll? If so use VS, it can debug your work even if its injected into wow. If you want to look at your dll with IDA just compile it as debug and the names should kick around. But other than that, I have no idea what you are trying to do lols....

Thanks, that's what i want. i just don't know compiling as debug , IDA will show their names automatically
But How can i debug dll with VS? Can VS inject DLL into WOW? or something else? Directly press F5 just show a msgbox "Can't run XXXXX.dll"

[Frosttall]

Thanks, that's what i want. i just don't know compiling as debug , IDA will show their names automatically
But How can i debug dll with VS? Can VS inject DLL into WOW? or something else? Directly press F5 just show a msgbox "Can't run XXXXX.dll"

Inject your dll and debug the wow-process you've injected.

[demonguy]

Inject your dll and debug the wow-process you've injected.

That's what I have done with Ida. But it's difficult to debug without function name in DLL

[Frosttall]

That's what I have done with Ida. But it's difficult to debug without function name in DLL

Build the dll in debug mode and attach your visual studio debugger...

[mansemino]

hmmm.. And what about compiling with LIB & MAP outputs, and use IDA tools to make a SIG file to parse names? (you know... getting a Flirt file with the FLAIR tools)...

Look for "how to make IDA signature files" on Google (I'm not allowed to post links.. first post )

[_Mike]

hmmm.. And what about compiling with LIB & MAP outputs, and use IDA tools to make a SIG file to parse names? (you know... getting a Flirt file with the FLAIR tools)...

Look for "how to make IDA signature files" on Google (I'm not allowed to post links.. first post )

Why would you do that if you already have a pdb file for the dll?

Like others have said already multiple times, change your project settings to compile with debug info:
c++ -> general -> debug information format: program database
linker -> debugging -> generate debug info: yes

and then attach VS to wow (debug menu, attach to process) and inject your dll.

And I would also recommend disabling optimizations or you will likely get incorrect results when trying to inspect variables.

[mansemino]

Why would you do that if you already have a pdb file for the dll?

As I understand, he wants to debug WoW with IDA (not the DLL). So, I think it is a solution as valid as any other.

[DarkLinux]

You cant really debug WoW with IDA. IDA is more of a decompiler. CE, Ollydbg and VS are debuggers.

[DrakeFish]

You cant really debug WoW with IDA. IDA is more of a decompiler. CE, Ollydbg and VS are debuggers.

IDA has an integrated debugger which I haven't used a lot but I suppose it could become useful if you want to map structures on runtime instead of doing them manually (or whatever else feature this could be good for), but I suppose other debuggers probably offer more feature.

[_Mike]

As I understand, he wants to debug WoW with IDA (not the DLL). So, I think it is a solution as valid as any other.

He wants symbol names for his dll. The pdb has that, and a lot more detailed info than you can get with flirt signatures.
Signature files are useful for detecting functions in binaries you don't have debug info for, but if you do have it then pdbs are superior in every way.