crash, the simplest is to run the program under gdb, reproduce the
steps leading to the crash and then issue a gdb "bt -a" command to
get the stack trace, attach it to the bug. Note that for the
- data to be really useful libvirt debug informations must be present
+ data to be really useful libvirt debug information must be present
for example by installing libvirt debuginfo package on Fedora or
Red Hat Enterprise Linux (with debuginfo-install libvirt) prior
to running gdb.</p>
<pre> # ps -o etime,pid `pgrep libvirt`
... note the process id from the output
# gdb /usr/sbin/libvirtd
-.... some informations about gdb and loading debug data
+.... some information about gdb and loading debug data
(gdb) attach $the_damon_process_id
....
(gdb) thread apply all bt
-.... informations to attach to the bug
+.... information to attach to the bug
(gdb)
</pre>
<ul>
<li>1 or "debug": asking the library to log every message emitted,
though the filters can be used to avoid filling up the output</li>
- <li>2 or "info": log all non-debugging informations</li>
+ <li>2 or "info": log all non-debugging information</li>
<li>3 or "warn": log warnings and errors, that's the default value</li>
<li>4 or "error": log only error messages</li>
</ul></li>
<ul>
<li>4: only errors</li>
<li>3: warnings and errors</li>
- <li>2: informations, warnings and errors</li>
+ <li>2: information, warnings and errors</li>
<li>1: debug and everything</li>
</ul></li>
<li>log_filters: defines logging filters</li>