search

lucasg / Dependencies

A rewrite of the old legacy software "depends.exe" in C# for Windows devs to troubleshoot dll load dependencies issues.
MIT License
9.08k stars 746 forks source link

Dependencies doesn't show all exported symbols, unlike Depends #100

Open dictoon opened 4 years ago

dictoon commented 4 years ago

With Dependencies 1.9.0.0:

On several occasion, I have noticed that Dependencies is not showing all explicitly exported symbols and I have to fire up the good ol' Depends to get the expected results.

Here's a concrete example:

Dependencies shows that the selected DLL explicitly exports 25 symbols:

image

While I know for a fact that many hundreds are exported, which Depends gets right:

image

(Sorry for all the pixelization, I can't show any of this publicly...)

Am I missing something?

lucasg commented 4 years ago

Can you test it with a recent build ? The 1.9 release was over a year ago, and I maybe fixed it in the meantime : https://ci.appveyor.com/project/lucasg/dependencies/builds/28547419/job/6p4vxru8vg53k84q/artifacts

You can also use the cli version Dependencies.exe -exports $your_binary and check if you manage to reproduce the bug (otherwise it's "just" a GUI issue).

If you manage to trigger the issue on "public" binaries I'm interested to take a look at it, otherwise I don't really see how I can track the root cause ...

FrancoisBeaune commented 4 years ago

Unfortunately I can no longer reproduce the issue with my current binary (it has continued to evolve after my tests). Both the latest official release and the master build that you linked to now show all symbols.

I did notice a couple other smaller issues that probably warrant their own tickets, can I open tickets for bugs in master?

lucasg commented 4 years ago

Unfortunately I can no longer reproduce the issue with my current binary (it has continued to evolve after my tests). Both the latest official release and the master build that you linked to now show all symbols.

Okay, I'll keep the ticket opened. Maybe someone else will trigger the same bug in the future

I did notice a couple other smaller issues that probably warrant their own tickets, can I open tickets for bugs in master?

Yep, I prefer not to mix several bugs in the same issue discussion. Tickets are free :)