Hmm, I've already sent a patch fixing this particular bug
https://lists.fedorahosted.org/pipermail/crash-catcher/2013-August/005276.html
On Mon, 2013-09-02 at 16:09 +0200, Richard Marko wrote:
This prevents abrt-handle-event from crashing when
satyr is unable to get crash thread of one of the
If you add a new element like this one (libreport_version) and remove %
reporter keyword, you will see version of libreport used to create the
dump directory but you won't see the version of libreport used to file
the bug tracking ticket. But we need to know even the later mentioned
version
On 09/09/2013 10:12 AM, Jakub Filak wrote:
If you add a new element like this one (libreport_version) and remove
%reporter keyword, you will see version of libreport used to create the
dump directory but you won't see the version of libreport used to file
the bug tracking ticket. But we need
Signed-off-by: Denys Vlasenko dvlas...@redhat.com
---
src/plugins/abrt-dedup-client.c | 24 ---
src/plugins/abrt-retrace-client.c | 134 --
src/plugins/https-utils.c | 17 -
src/plugins/https-utils.h | 4 +-
4 files changed, 72
Signed-off-by: Michal Toman mto...@redhat.com
---
lib/abrt.c | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/lib/abrt.c b/lib/abrt.c
index 53f84cd..f7d9824 100644
--- a/lib/abrt.c
+++ b/lib/abrt.c
@@ -456,10 +456,13 @@ sr_abrt_report_from_dir(const char *directory,
CLARIFICATION:
I don't insist on usage of %reporter keyword but I want to see the
reporter version.
On Mon, 2013-09-09 at 12:52 +0200, Denys Vlasenko wrote:
On 09/09/2013 10:12 AM, Jakub Filak wrote:
If you add a new element like this one (libreport_version) and remove
%reporter keyword,
On 08/26/2013 09:28 AM, Jakub Filak wrote:
abrt-dump-location.path starts abrtd.service whenever the dump location
changes in order to ensure that the directory exists and has right
Selinux context, UID and GID.
If /var/tmp/abrt is deleted and something crashes following happens:
Sep 09
Pushed, thanks!
On 09/01/2013 08:09 PM, Denys Vlasenko wrote:
I've seen strange BZ created by abrt where exploitable element
looked bogus. It claimed that the crash was jumping to bogus address
yet crashing insn was a benign reg-to-reg move.
This patch makes analyzer to record what it thinks
Pushed, thanks!
On 09/01/2013 08:12 PM, Denys Vlasenko wrote:
Signed-off-by: Denys Vlasenko dvlas...@redhat.com
---
src/plugins/abrt-dump-oops.c | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/src/plugins/abrt-dump-oops.c b/src/plugins/abrt-dump-oops.c
index
Signed-off-by: Denys Vlasenko dvlas...@redhat.com
---
po/POTFILES.in | 1 +
src/cli/abrt-cli-core.c | 58 +
src/cli/abrt-cli-core.h | 4
src/cli/list.c | 57
src/cli/report.c
10 matches
Mail list logo