Matching cdl64 symbols from _bugreport.txt
-
On 22/01/2017 at 13:16, xxxxxxxx wrote:
User Information:
Cinema 4D Version: R17
Platform: Windows ;
Language(s) : C++ ;---------
Hi!I have a Windows _bugreport.txt with a crash stack, the cd64 library and the full x64_Release folder.
How can I match the stack symbols to the actual symbol name?symchk won't open it (says pdb is mismatched or not found)
Dependency Walker (suggested here) lists only c4d_main, nothing more.
CFF Explorer gives no clue whatsoever.Is there any recommendation to make our lives easier for this kind of situation?
-
On 23/01/2017 at 09:29, xxxxxxxx wrote:
Hi,
That's not possible because we don't publish the symbol files of Cinema 4D.
But you should be able to see the symbols of your plugin if you don't strip away the symbol information. -
On 23/01/2017 at 12:16, xxxxxxxx wrote:
I just want to see the symbols for my plugin, not for Cinema 4D.
Even if it's stripped, should be on the pdb file, right?I develop for mac for a long time but I'm new to Windows, and can't find a way to match the cdl64 and pdb.
-
On 23/01/2017 at 12:33, xxxxxxxx wrote:
btw, what's the option to not strip symbols?
Debug builds also have no symbols, on the rare cases when C4D detect them.
I'm using the R16 sdk template. -
On 24/01/2017 at 03:41, xxxxxxxx wrote:
Symbols aren't stripped by default and the Debug build of your plugin should have symbols generated.
Do you have the minidump.dmp file for the bug report?
If you're developing for R17 you should use the R17 cinema4dsdk project template, not the one from R16.
Note Visual Studio 2013 is the supported development environment under Windows for R17. -
On 27/01/2017 at 11:29, xxxxxxxx wrote:
Originally posted by xxxxxxxx
Do you have the minidump.dmp file for the bug report?
Yes, I have the minidump, what can I do with it?
If I force a crash on my machine, I do see the symbols on _BugReport.txt
But none of my user's bug reports have symbols.So, I have the cdl64/dll and the full x64_Release folder.
Is there any way to get the symbols from that stack?MyPlugin.cdl64: c4d_main + 0xc966 (SP: 0x000000D2E5B3AE50, PC: 0x00007FF95F51E816)
MyPlugin.cdl64: c4d_main + 0x6b51 (SP: 0x000000D2E5B3AEB0, PC: 0x00007FF95F518A01)
MyPlugin.cdl64: c4d_main + 0xba1a (SP: 0x000000D2E5B3AFF0, PC: 0x00007FF95F51D8CA)
MyPlugin.cdl64: c4d_main + 0x299fa (SP: 0x000000D2E5B3B230, PC: 0x00007FF95F53B8AA)