+++ This bug was initially created as a clone of Bug #635706 +++

--- Additional comment from pcarrier on 2010-11-15 00:35:06 GMT ---

On a more general note, I had a look at the various options available.

We could even go further and gather infos+backtraces, with something along the lines of (to be Pythonized):

for ID in $(sqlite3 /var/spool/abrt/abrt-db 'select UUID from abrt_v4')
do
  abrt-cli -ib $ID
done

I don't have a strong opinion for or against it, and would be happy to get feedback on that.


Cheers,

-- 
Pierre

--- Additional comment from pcarrier on 2010-11-15 00:42:51 GMT ---

Elements if we want to go further with the idea from my comment 4:

1) abrt-cli doesn't offer any clean way to list the UUID unless we want to parse the 'abrt -lf' output

2) No Python for the sqlite3 request as far as I'm concerned, as Red Hat doesn't ship Python support for sqlite3 in RHEL6;

3) However it seems safe to rely on /usr/bin/sqlite3 in this plugin.
Ran under RHEL6:
# rpm -q --requires abrt|grep sql;rpm -qf /usr/lib64/libsqlite3.so.0; rpm -qf /usr/bin/sqlite3
libsqlite3.so.0()(64bit)
sqlite-3.6.20-1.el6.x86_64
sqlite-3.6.20-1.el6.x86_64

-- 
Pierre