| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
- so far used only by kerneloops
|
|
|
|
|
|
|
|
|
|
|
|
| |
For most users, "hostname" is the same for every crash (it is their hostname).
Not every problem even has "Application" field ("low on disk space" problem,
for example, doesn't), whereas any problem should have "Reason" field.
For non-root, it is useful to see which dumps are in /var/spool/abrt
(and aren't writable), and which are in $HOME/.abrt/spool.
Signed-off-by: Denys Vlasenko <dvlasenk@redhat.com>
|
|
|
|
| |
Signed-off-by: Denys Vlasenko <dvlasenk@redhat.com>
|
|
|
|
| |
Signed-off-by: Denys Vlasenko <dvlasenk@redhat.com>
|
|
|
|
| |
Signed-off-by: Denys Vlasenko <dvlasenk@redhat.com>
|
|
|
|
|
|
|
|
| |
This makes python wrappers more usable.
src/report-python/test_full demonstrates how pyhton
programs can run reporting now.
Signed-off-by: Denys Vlasenko <dvlasenk@redhat.com>
|
|
To be exact, these three functions are renamed:
load_crash_data_from_crash_dump_dir
create_crash_dump_dir
delete_crash_dump_dir
Rationale: data structure is called "struct dump_dir", not
"struct crash_dump_dir"
Signed-off-by: Denys Vlasenko <dvlasenk@redhat.com>
|