summaryrefslogtreecommitdiffstats
path: root/src/plugins
diff options
context:
space:
mode:
Diffstat (limited to 'src/plugins')
-rw-r--r--src/plugins/analyze_LocalGDB.xml.in3
-rw-r--r--src/plugins/analyze_RetraceServer.xml.in4
2 files changed, 7 insertions, 0 deletions
diff --git a/src/plugins/analyze_LocalGDB.xml.in b/src/plugins/analyze_LocalGDB.xml.in
index 54209e70..f85072d0 100644
--- a/src/plugins/analyze_LocalGDB.xml.in
+++ b/src/plugins/analyze_LocalGDB.xml.in
@@ -2,4 +2,7 @@
<event>
<_name>Local GNU Debugger</_name>
<_description>Download debuginfo packages and generate backtrace locally using GDB</_description>
+ <_long_description>Needs to downloads debuginfo packages, which might take significant time, and take up disk space.
+ However, unlike RetraceServer, doesn't send coredump to remote machines.
+ </_long_description>
</event>
diff --git a/src/plugins/analyze_RetraceServer.xml.in b/src/plugins/analyze_RetraceServer.xml.in
index b3c7da24..7f7f0362 100644
--- a/src/plugins/analyze_RetraceServer.xml.in
+++ b/src/plugins/analyze_RetraceServer.xml.in
@@ -2,6 +2,10 @@
<event>
<name>Retrace Server</name>
<_description>Send core dump to remote retrace server for analysis</_description>
+ <_long_description>Uploads coredump to a server, which generates backtrace and returns it.
+ Pros: no need for debuginfo downloads. Retrace server's database of debuginfos is more complete. Retrace server may generate better backtraces.
+ Cons: coredump you upload contains all the data from the crashed program, including your private data, if any.
+ </_long_description>
<options>
<option type="text" name="RETRACE_SERVER_URL">
<_label>Retrace server URL</_label>