| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
elements of dump directory.
This patch changes it to generic handling, where abrt-cli doesn't know
anything about particular elements (like backtrace).
Changes in detail:
* crash_item->flags how has CD_FLAG_UNIXTIME bit.
* format_crash_item(item) returns malloced formatted string
(currently only formatted time for items with CD_FLAG_UNIXTIME)
or NULL, if item->content is to be used as-is
* crash_item->flags how has CD_FLAG_LIST bit, it is set on a
small number of elements which are to be shown by abrt-cli -l.
* abrt-cli -l doesn't use fixed names, it looks at CD_FLAG_LIST.
* abrt-cli -i doesn't use fixed names, it prints all one-line elements:
Directory : /var/spool/abrt/ccpp-1298264192-2705
analyzer : CCpp
architecture : x86_64
cmdline : metacity
comment : Abrt testing, please disregard
component : metacity
coredump : /var/spool/abrt/ccpp-1298264192-2705/coredump
count : 1
crash_function : pa_atomic_load
executable : /usr/bin/metacity
global_uuid : 1e8b716d2094fb22dccdb5321ac0cf6f14eb6689
hostname : dhcp-25-227.brq.redhat.com
kernel : 2.6.34.7-61.fc13.x86_64
os_release : Fedora release 13 (Goddard)
package : metacity-2.30.0-3.fc13
rating : 4
reason : Process /usr/bin/metacity was killed by signal 11 (SIGSEGV)
time : Mon 21 Feb 2011 05:56:32 AM CET
uid : 500
uuid : 453085d0f703b96ddc3a5172dd7d5a29479f5b3f
* abrt-cli -i --backtrace is removed. Instead, abrt-cli -i --full
is to be used. It shows all elements, one-line and multi-line ones.
* abrt-cli code now has an example how to list crast_data_t
in the sorted-by-key order.
Further ideas:
abrt-cli needs -o elem1,elem2,elem3 option which tells which elements to
show, and/or -O elem1,elem2,elem3 option which tells elements to NOT
show. Rationale: abrt-cli -i --full output is way too long because of
smaps, need a way to suppress unneeded elements display
Signed-off-by: Denys Vlasenko <dvlasenk@redhat.com>
|
|
|
|
| |
Signed-off-by: Denys Vlasenko <dvlasenk@redhat.com>
|
|
|
|
| |
Signed-off-by: Nikola Pajkovsky <npajkovs@redhat.com>
|
| |
|
|\ |
|
| |\ |
|
| | |
| | |
| | |
| | | |
Signed-off-by: Nikola Pajkovsky <npajkovs@redhat.com>
|
| | |
| | |
| | |
| | | |
Signed-off-by: Nikola Pajkovsky <npajkovs@redhat.com>
|
| | |
| | |
| | |
| | | |
Signed-off-by: Nikola Pajkovsky <npajkovs@redhat.com>
|
| |/
| |
| |
| |
| | |
- also added default event configuration for rhtsupport
- and tweaked a spec file a little
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Currently the duplicate hash of a crash for Bugzilla is computed from
the package NVR (name, version, release), path of the executable, and
the backtrace hash.
This is very unfortunate because the package NVR is changed frequently
(it contains Fedora OS version), and path of the executable is not a
good differentiator. When multiple executables from a single component
crash with similar backtrace, it is better to assume that they share
code and have single Bugzilla bug report.
This commit changes the code to compute the duplicate hash from the
component name and the backtrace hash.
|
|\
| |
| |
| |
| |
| |
| | |
* cli:
cli: show screen_name when abrt asks for reporters
cli: report.cpp -> report.c
cli: remove last c++ism
|
| |
| |
| |
| | |
Signed-off-by: Nikola Pajkovsky <npajkovs@redhat.com>
|
| |
| |
| |
| |
| |
| | |
no code changed
Signed-off-by: Nikola Pajkovsky <npajkovs@redhat.com>
|
| |
| |
| |
| | |
Signed-off-by: Nikola Pajkovsky <npajkovs@redhat.com>
|
|\ \ |
|
| |/ |
|
|\| |
|
| |
| |
| |
| |
| |
| |
| | |
Closes #188 "-d should be documented as a root-only, or made to work for user".
Also might make testing easier.
Signed-off-by: Denys Vlasenko <dvlasenk@redhat.com>
|
| |\
| | |
| | |
| | |
| | | |
* daemon/blacklist:
rhbz#692465 - Blacklist doesn't work
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
parse_value() doesn't trim the string.
Lest say BlackList = coreutils, mono
the parsed list looks like -> 'coreutils', ' mono'
Signed-off-by: Nikola Pajkovsky <npajkovs@redhat.com>
|
| | |
| | |
| | |
| | | |
Signed-off-by: Denys Vlasenko <dvlasenk@redhat.com>
|
|/ / |
|
| | |
|
|/ |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
$ abrt-dump-oops -d -o Downloads/examples_oops1.test
abrt-dump-oops: Found oopses: 1
[...]
abrt-dump-oops: Creating dump directories
abrt-dump-oops: Can't create directory '/var/spool/abrt/oops-...': Permission denied
abrt-dump-oops: 1 errors while dumping oopses
[newman@dhcp-24-178 ~]$ echo $?
0
Signed-off-by: Nikola Pajkovsky <npajkovs@redhat.com>
|
|\ |
|
| | |
|
| |
| |
| |
| | |
Signed-off-by: Nikola Pajkovsky <npajkovs@redhat.com>
|
|/ |
|
|
|
|
| |
libreportgtk.so versioned libraries
|
| |
|
| |
|
|
|
|
|
|
|
| |
- seems like server_has_persistence() returns false when it's called
at the time of applet start, my guess is that the notifyd service setup
is not finished at this time, so I moved applet init to the time of
the first crash, where all the desktop/notifyd thing should be ready
|
|
|
|
| |
Signed-off-by: Nikola Pajkovsky <npajkovs@redhat.com>
|
|
|
|
| |
Signed-off-by: Nikola Pajkovsky <npajkovs@redhat.com>
|
|
|
|
| |
Signed-off-by: Nikola Pajkovsky <npajkovs@redhat.com>
|
|
|
|
| |
Signed-off-by: Nikola Pajkovsky <npajkovs@redhat.com>
|
|
|
|
|
|
|
|
|
|
|
|
| |
solution isn't good enough, but truly remove misleading message. Imagine
the situation when user manually set environment Bugzilla_Password and manually
run command a-a-b -c /path/to/config1 -c /path/config2 -c /path/config3.
Now a-a-b smash all configs into one giant hash table. Just stir the pot.
Environment can be set by cli and gui. We have a lot of input how to set
config and question is how to determinate which config is wrong and blame
someone/something.
Signed-off-by: Nikola Pajkovsky <npajkovs@redhat.com>
|
|
|
|
| |
Signed-off-by: Nikola Pajkovsky <npajkovs@redhat.com>
|
| |
|
| |
|
| |
|
|
|
|
| |
This reverts commit e2b73a97a213d6b317e5410b0dc9d931686442d2.
|
| |
|
|
|
|
| |
Signed-off-by: Nikola Pajkovsky <npajkovs@redhat.com>
|
|
|
|
| |
backtrace
|
|
|
|
| |
remove dead code
|
| |
|
|
|
|
| |
trac#127
|