- Last Active
- Members, Staff
We'll need the complete error message, (hex number included), with all following information, (it tells us the function, file and line number inside Insure++ so we can determine the cause), and the complete Insure++ version number, which is easily accessed by simply typing "insure" with no arguments. Be sure to include the build date.
If this is reproducible, then it will help if we can get a stack back trace. Run your application under "gdb" and when it halts, (this is actually an Insure++ panic), get a back trace of all threads, (gdb command: "thread apply all bt").
Capture the back trace in a file, and attach that file to your email or the support ticket.
--Rich, Lead Engineer, Insure++1
Mark had a slight typo above in this sentence:
"We are currently in the final stages of preparing a beta release of Insure++ for VS2010, targeted for January 30th."
He meant, of course, "... Insure++ for VS2015, targeted..."