ImportBugReport doesn't import CallStacks?
Posted: Sun May 20, 2018 11:07 am
Dear Mathias,
The background
===
I'm implementing a custom madExcept exception viewer for exception messages collected from users.
I use the IMEException interface instance returned by ImportBugReport(), and I have successfully displayed the general exception summary (such as Exception Message, User's OS, etc) through IMEException.BugReportHeader.
The issue
===
And I'm having an issue for the second step - to show the call stacks. I first tried to read IMEException.CallStacks, but it's empty.
I debugged into madExcept.pas, and it seems that TIMEException.GetBugReportSections.PrepareThreadReport() where the call stacks are pared is not called, not sure why.
Am I going the wrong direction? Thanks.
Also, How do I get the thread name (something like "main thread ($1fe0)" of IMEException.CallStacks?
Thank you very much in advance.
---------------------
ps: madException version: The latest madCollection-2.8.4.0 with MadException 4.0.19
ps2: I confirm IMEException.BugReportSections does seem to contain the correct string content.
The background
===
I'm implementing a custom madExcept exception viewer for exception messages collected from users.
I use the IMEException interface instance returned by ImportBugReport(), and I have successfully displayed the general exception summary (such as Exception Message, User's OS, etc) through IMEException.BugReportHeader.
The issue
===
And I'm having an issue for the second step - to show the call stacks. I first tried to read IMEException.CallStacks, but it's empty.
I debugged into madExcept.pas, and it seems that TIMEException.GetBugReportSections.PrepareThreadReport() where the call stacks are pared is not called, not sure why.
Am I going the wrong direction? Thanks.
Also, How do I get the thread name (something like "main thread ($1fe0)" of IMEException.CallStacks?
Thank you very much in advance.
---------------------
ps: madException version: The latest madCollection-2.8.4.0 with MadException 4.0.19
ps2: I confirm IMEException.BugReportSections does seem to contain the correct string content.