Error Report doesn't show line details because "A PDB was not provided..."
mwfs
Posts: 1 New member
I am using version 8.3.2.5689 of SmartAssembly (currently the latest version, but I believe I've had this issue for a long time and with previous versions).
I have the automated error reporting with a custom template enabled which is generating a .sareport file. I have it configured for the several DLLs to be merged into the main EXE with obfuscation, pruning, dynamic proxy, resource compression and encryption, etc. Some DLLs may not have a PDB file, but the one that is erroring does have a PDB.
For some reason, when I view a sareport file that is generated by an error, it says "The line number is not available. A PDB file was not provided when SmartAssembly processed the assembly."
I believe I know which DLL errored just by the class name in the stack trace. The main EXE file and the DLL that contains the code that errored both have their PDB files in the same directory when SmartAssembly processed and merged them. How can I figure out what PDB file is missing that would cause this? Could it be an incorrect error message about the PDB missing?
I do not have "Generate debugging information" enabled, but it says "you do not need to generate a pdf file if you are using error reporting feature" - so it is my understanding that I do not need this enabled.
Thanks for any advice.
I have the automated error reporting with a custom template enabled which is generating a .sareport file. I have it configured for the several DLLs to be merged into the main EXE with obfuscation, pruning, dynamic proxy, resource compression and encryption, etc. Some DLLs may not have a PDB file, but the one that is erroring does have a PDB.
For some reason, when I view a sareport file that is generated by an error, it says "The line number is not available. A PDB file was not provided when SmartAssembly processed the assembly."
I believe I know which DLL errored just by the class name in the stack trace. The main EXE file and the DLL that contains the code that errored both have their PDB files in the same directory when SmartAssembly processed and merged them. How can I figure out what PDB file is missing that would cause this? Could it be an incorrect error message about the PDB missing?
I do not have "Generate debugging information" enabled, but it says "you do not need to generate a pdf file if you are using error reporting feature" - so it is my understanding that I do not need this enabled.
Thanks for any advice.
