Re: [Dev] Tizen 3.0 : Optimizing applications launch time

[Dominig ar Foll (Intel OTC)]

Le 24/10/2013 20:42, Peters, Brad T a écrit : Hi Stéphane, I'm a fervent believer in first-crash data capture, especially when you're environment is  unstable to begin with (ie 3.0). Installing debug packages after the fact requires  reproducing the issue, which may or may not happen and wastes time. That said, it looks like 3.0 binaries are already partially stripped (check out this patch: https://review.tizen.org/gerrit/gitweb?p=platform/upstream/rpm.git;a=commit;h=343c985ee3f8e027386fec73da1c63f827e48a03 ) Main issue with the current model is that all the QA is done with a model which is not in line with a product target and that is wrong. Memory size and load timing changes can induce bugs which are very tricky. Best model is to test as close as possible from a deployment model and to provide the method to do the debug by adding the symbol on demand. It seems that debug (in line or post mortem) with external symbol files are not well understood and spending a bit of time to get some documentation would help. But leaving the symbol in until productisation is certainly not a good idea in order to quickly converge to a shipping quality. Dominig

_______________________________________________
Dev mailing list
Dev@lists.tizen.org
https://lists.tizen.org/listinfo/dev