-
Type:
Story
-
Status: Resolved
-
Priority:
Minor
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: 2.1.0
-
Component/s: None
-
Labels:None
During some of the investigations of crash reports, we had problems finding out where the application actually had crashed, since the log file will only show an instruction pointer. Also with a crash on a particular location, it is very helpfull to know what the other threads are doing as this gives concurrency information and details on which sequence of event trigger something. Especially with hard to reproduce problems a better trace would be helpfull.
I would like to see a backtrace per thread upon any serious fault.