New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Npcap debug symbols package do not include wpcap.pdb #1844
Comments
Thanks for this report. The inclusion of wpcap.dll is an unfortunate artifact of our build system not finding a PDB file for that DLL. This is because libpcap's build does not generate one by default. I need to investigate how to instruct it to do so, preferably using CMake command-line options, so that we can fix this. I did not realize the impact it had on profiling. |
I don't remember anything special about getting the |
Or just by default without command-line options, i.e. generate them for all builds unless explicitly told not to. (It's not as if PDB files shouldn't be shipped with libpcap because it would help people reverse-engineer libpcap. :-)) Or is this just an issue of Release vs. RelWithDebInfo builds? Is the idea that Release builds shouldn't include debug information but RelWithDebInfo builds should? Or do Release builds generate less detailed sets of debug symbols than do RelWithDebInfo builds? |
Which project - libpcap or Npcap? libpcap should work with VS 2015, 2017, or 2019; if not, that's a bug that should be fixed.
Release, Debug, or RelWithDebInfo build? |
My build directory shows that I compiled both Debug and RelWithDebInfo. I profiled with RelWithDebInfo (as profiling Debug builds isn't as useful). The pdbs I found were in |
Debug symbols package for Npcap 0.9991 includes PDBs for wpcap.dll from our installer. Thanks for your help! |
Is that in the npcap.pdb file? |
Instead of
wpcap.pdb
the debug symbols package includeswpcap.dll
. This makes it difficult to profile the performance (e.g. #1551) for people who do not have Npcap development environment set up (and thus are able to build their ownwpcap.dll
and matchingwpcap.pdb
).Visual Studio profiler basically stops at first
.dll
for which symbols are not available. And thus even though thePacket.pdb
is available the calls do not seem to be be available in analysis if they are called via calls towpcap.dll
.The text was updated successfully, but these errors were encountered: