Júlio Maranhão wrote, On 2008-05-24 15:33: > I will try to discover tools to isolate the problem (certs, PKCS#11 > module, NSS, PSM, TB).
I'd start by logging the calls and returns for your PKCS #11 module. Look here for directions on using the module trace facility: http://www.mozilla.org/projects/security/pki/nss/tech-notes/tn2.html >> The MSVC compilations produce debug binaries (.exe or .dll files, and .pdb >> files). The debugger built into MSVS 2005 does full source-level debugging >> (no assembly code required, except for those functions that are written in >> assembly language) using the binaries built that way. It's a very rich and >> powerful source debugger. > > I cannot make VS 2005 show the source code while debugging an executable > that was not created by a VS project. VS does not know where are the > source code. Is this problem only for NSS? or for all the files you built? Are the .pdb files located in the same directory with the .exe and .dll files? Is it possible that you're running a different executable than the one you built? Is there a copy of Thunderbird in your path that is being used instead of the copy you build? >> I don't build the entire Thunderbird product, the way you did. I only >> work on NSS, so I only build NSS. I download "nightly" builds of the >> programs with which I want to test NSS, such as Thunderbird, and I replace >> the downloaded NSS binaries with the ones I built, then I debug. As long >> as I only try to set breakpoints in the code I actually compiled. it works >> fine. I should have added that, for Firefox and SeaMonkey, I can do source level debugging in all of the browser, without having to build it all, by using Mozilla's symbol server, from which the debugger can download the .pdb files. As long as I have the sources on my machine, I can debug the code, even though I did not build it. But I do not know if that symbol server includes Thunderbird build symbols or not, and there is no way to browser or explore it to find out. :( > I will use some pkcs#11 tool from NSS to test my module. The module trace facility, which is part of any debug build, should be a big help. _______________________________________________ dev-tech-crypto mailing list [email protected] https://lists.mozilla.org/listinfo/dev-tech-crypto
