Is it possible to include component names in the calll stack?
Posted: Wed May 25, 2022 7:39 am
When our customers send bug reports, we sometimes get call stacks like this:
TcxTimer.SetEnabled in cxClasses:1401
TcxCustomButton.MouseUp in cxButtons:1987
TControl.DoMouseUp in Vcl.Controls:7724
TControl.WMLButtonUp in Vcl.Controls:7737
TControl.WndProc in Vcl.Controls:7480
TWinControl.WndProc in Vcl.Controls:10424
TButtonControl.WndProc in Vcl.StdCtrls:5439
TcxCustomButton.WndProc in cxButtons:1744
TWinControl.MainWndProc in Vcl.Controls:10113
StdWndProc in System.Classes:18175
DispatchMessageW in USER32.dll
TApplication.ProcessMessage in Vcl.Forms:11028
TApplication.HandleMessage in Vcl.Forms:11058
TApplication.Run in Vcl.Forms:11196
initialization in Cw:352
BaseThreadInitThunk in KERNEL32.DLL
As you can see, there are no names anywhere, just types. We have many TcxTimers and TcxCustomButtons, but this call stack doesn't help us see which timer/button led to the error, not even which form it came from. Is there any way to include this information in the bug report?
TcxTimer.SetEnabled in cxClasses:1401
TcxCustomButton.MouseUp in cxButtons:1987
TControl.DoMouseUp in Vcl.Controls:7724
TControl.WMLButtonUp in Vcl.Controls:7737
TControl.WndProc in Vcl.Controls:7480
TWinControl.WndProc in Vcl.Controls:10424
TButtonControl.WndProc in Vcl.StdCtrls:5439
TcxCustomButton.WndProc in cxButtons:1744
TWinControl.MainWndProc in Vcl.Controls:10113
StdWndProc in System.Classes:18175
DispatchMessageW in USER32.dll
TApplication.ProcessMessage in Vcl.Forms:11028
TApplication.HandleMessage in Vcl.Forms:11058
TApplication.Run in Vcl.Forms:11196
initialization in Cw:352
BaseThreadInitThunk in KERNEL32.DLL
As you can see, there are no names anywhere, just types. We have many TcxTimers and TcxCustomButtons, but this call stack doesn't help us see which timer/button led to the error, not even which form it came from. Is there any way to include this information in the bug report?