http://mvidner.blogspot.com/2008/04/opensuse-110-beta-1-is-that-murderers.ht... I like the idea of that, and it actually already helped me to track down some bugs. But I have one request for that: Could we somehow make it more visible which log lines were released later, and where the segfault occurred? Currently IMHO it's very hard to find that dividing line: There is a lot of noise from the YCP interpreter (it even dumps the entire code to the log that is being executed - a bit overkill IMHO) and other libs. I'd like some indentation (some blanks or a tab) for those released log lines. Is that feasible? Failing that, some blank lines (4-5) and a marker would also be helpful so you can see quickly while scrolling where those released debug log lines begin: 2008-04-28 17:27:11 <0> snell(18431) [qt-ui] YQApplication.cc(YQApplication):61 YQApplication constructor end 2008-04-28 17:27:11 <1> snell(18431) [qt-ui] YQUI_core.cc(initUI):243 YQUI initialized. Thread ID: 0xb685fb90 2008-04-28 17:27:11 <0> snell(18431) [qt-ui] YQMainWinDock.cc(YQMainWinDock):57 MainWinDock initial size: 895 x 683 *** SEGFAULT *** Releasing suppressed debug log lines: 2008-04-28 17:27:10 <0> bla... 2008-04-28 17:27:10 <0> bla... 2008-04-28 17:27:10 <0> bla... 2008-04-28 17:27:10 <0> bla...

...

...

End of suppressed debug log lines

2008-04-28 17:27:10 <1> ...log from another y2base process... CU -- Stefan Hundhammer <sh@suse.de> Penguin by conviction. YaST2 Development SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Nürnberg, Germany -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org