Getting support¶

First diagnostic¶

If EKG2 segfaults, it tries to write as much data as it can — including updating and closing logs, writing all debug data, configuration and dumping core. All of these files are written in ~/.ekg2 and have PID appended to their names (excluding corefile, which has it only on RH). This time also debug data would be very helpful, as well as corefile.

It'd be also nice to note if problem can be reproduced and how, and whether it still appears in fresh SVN version (or snapshot).

h3. Getting backtrace

Coredump itself is too big to be delivered to authors. Thus, it'll be your job to extract meaningful information from it. When reporting a bug, the most important data contained in coredump is backtrace. To read it, you'll need "gdb":http://sourceware.org/gdb/.

<pre>
gdb <PATH_TO_EKG2_BINARY> <PATH_TO_CORE_FILE>
</pre>
e.g.:
<pre>
gdb /usr/local/bin/ekg2 ~/.ekg2/core
</pre>

If provided path is correct, gdb should read symbols from few libraries and then display shell. Please note that you'd have to use exact the same binary (and plugins) as at the moment coredump was created. Else gdb won't be able to read it correctly. If everything went right, now enter:
<pre>
bt full
</pre>

<pre>

h3. Using valgrind

Another good method of diagnosing problems is running EKG2 under "valgrind":http://valgrind.org/ memcheck tool. In EKG2 sources 'contrib' dir there is 'vekg' script, allowing you to easily start EKG2 under valgrind:
<pre>
contrib/vekg <EKG2_ARGS>
</pre>

<pre>

h2. Reporting bugs ==
 Trac ===
You can report a bug using "Trac":http://bugs.ekg2.org/newticket. When describing a bug, please be as verbose as possible — especially including OS and distribution, used plugins, used librararies (and their versions) if you think they can be source of problem. Please include debuginfo output by EKG2 (please note that it can sometimes contain plaintext passwords (e.g. in GTalk), so please first remove them), backtrace, valgrind logs…

h3. Mailing lists

Another way of reporting bugs and contacting developers is through mailing lists. More information can be found on "contact page":http://ekg2.org/contact.php.

h3. IRC

<pre>