On Mon, Jan 18, 2010 at 02:45:33PM +0100, Jiri Moskovcak wrote: > On 01/18/2010 02:18 PM, James Antill wrote: > >On Mon, 2010-01-18 at 11:19 +0100, Jiri Moskovcak wrote: > >>>Currently ABRT can at least run `rpm -qf MAIN_EXECUTABLE > >>>ALL_GDB_INFO_SHARED_DISPLAYED LIBRARIES FILENAMES' and report these nvrs in > >>>the Bugzilla bugreport before such build-id -> nvr server is deployed. > > > > This should use the yum API, IMO. Then you can output the yumdb info. > >(esp. from_repo). Also on newer yum's it'd be nice to run "yum check" > >and also "needs-restarting" (from newer yum-utils). > > > > Ok, I think we can add this. > > > Also it'd be nice if the python tracebacks weren't in attachments, > >given that they are plain text. > > > > Since abrt 1.0.0 (maybe 1.0.1) the backtrace is added as a comment > if it's shorter than 2 kilobytes What if you always add a portion of the complete stack as a comment? Let's say first n lines/kilobytes of the thread where the crash happened. Of course, it could be limited to situations where there is any useful information in the stack. There is no need to do this if all the stack contains is useless question marks... D. -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
