abrt.git - Unnamed repository; edit this file 'description' to name the repository.

	Commit message (Collapse)	Author	Age	Files	Lines
*	assorted cleanups, memory leak fix (g_list_free in add_basics_to_problem_data)	Denys Vlasenko	2011-05-22	1	-12/+2
\| \| \| \|	Signed-off-by: Denys Vlasenko <dvlasenk@redhat.com>
*	move $ABRT_foo checking and setting into helper routines.	Denys Vlasenko	2011-05-04	1	-11/+3
\| \| \| \| \| \| \|	I'm sick of fixing incorrect PROGNAME defines. Now g_progname is a variable and it is set from argv[0]. Signed-off-by: Denys Vlasenko <dvlasenk@redhat.com>
*	add abrt-action-analyze-backtrace manpage. Closes #227	Denys Vlasenko	2011-05-03	1	-1/+1
\| \| \| \|	Signed-off-by: Denys Vlasenko <dvlasenk@redhat.com>
*	switch python and oops hashing to sha1	Denys Vlasenko	2011-04-18	1	-8/+6
\| \| \| \| \| \| \|	Update sha1 code to a smaller version. Verified that ccpp hashing produces the same results as the old code. Signed-off-by: Denys Vlasenko <dvlasenk@redhat.com>
*	Better duplicate hash	Karel Klic	2011-04-07	1	-13/+14
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	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.
*	abrt-action-analyze-backtrace: report failure when run on a dump_dir without ↵	Karel Klic	2011-03-28	1	-1/+7
\| \| \| \|	backtrace
*	abrt-action-analyze-backtrace: log backtrace parser failure every time; ↵	Karel Klic	2011-03-28	1	-8/+2
\| \| \| \|	remove dead code
*	Analyze backtraces from retrace server	Karel Klic	2011-03-26	1	-0/+190
	Hi, the attached patch splits a part of abrt-action-generate-backtrace to a new tool abrt-action-analyze-backtrace, which is used by both LocalGDB and RetraceServer analyzers. Then new abrt-action-analyze-backtrace tool reads backtrace and generates duplication hash, detects crash function, and provides backtrace rating. These steps haven't been performed for remotely analyzed crashes so far. Karel