sitter added a comment.

  Quick recap from what we talked about on telegram: putting the print after 
the bt is most definitely going to throw off the backtrace parsing logic, so 
doing it this way would require extensive changes there, which is a dangerous 
place to make extensive changes.
  Or we could define a simple function to ignore errors 
https://stackoverflow.com/questions/17923865/gdb-stops-in-a-command-file-if-there-is-an-error-how-to-continue-despite-the-er
 but that's also a bit faffy.
  Another completely standalone approach would be to change BacktraceGenerator 
(I think?) to invoke the print in a completely independent gdb invocation i.e. 
separate the print call from the regular batchcommands and have drkonqi 
assemble it back into the final report. That way the actual tracing batch 
command couldn't fail on the print.

REPOSITORY
  R871 DrKonqi

REVISION DETAIL
  https://phabricator.kde.org/D28129

To: apol, #frameworks, broulik, sitter
Cc: plasma-devel, Orage, LeGast00n, The-Feren-OS-Dev, cblack, jraleigh, zachus, 
fbampaloukas, GB_2, ragreen, ZrenBot, ngraham, himcesjf, lesliezhai, 
ali-mohamed, jensreuterberg, abetts, sebas, apol, ahiemstra, mart

Reply via email to