Re: [Evolution] Debugging theme comflict
- From: Ralf Mardorf <ralf mardorf rocketmail com>
- To: evolution-list gnome org
- Subject: Re: [Evolution] Debugging theme comflict
- Date: Sat, 13 Dec 2014 20:05:51 +0100
On Sat, 2014-12-13 at 19:42 +0100, Roy Reese wrote:
Running Evo 3.12.8 under Manjaro
have looked at the wiki, but am still unsure how to do it.
What exactly don't you understand? If you would ask more precise it
would be possible to help you more precise.
Doesn't the below information help? If not, what don't you understand?
http://bit.ly/1DsUzzJ
"Debugging Evolution's Crashes (Getting a backtrace)
If Evolution crashes, and you can reproduce it, than start Evolution in
a debugger like gdb:
gdb evolution
Once gdb is running, you can do the following steps:
Type "run" after gdb starts and attempt to reproduce the crash.
Take note of the output in gdb.
Type "thread apply all bt" to see more information about what went
wrong.
Including the debugging info acquired through the above method in a bug
report in Bugzilla will enable the developers pinpoint where something
is going wrong, hopefully making it easier to fix the bug in Evolution."
- https://projects-old.gnome.org/evolution/bugs.shtml
IIUC Manjaro is based on Arch Linux, so
http://bit.ly/1DsVGzz
"PKGBUILD
In order to build a package from source, the PKGBUILD file is required.
See ABS for packages in the official repositories, and
AUR#Acquire_build_files for packages in the AUR.
Compilation settings
At this stage, you can modify the global configuration file of makepkg
if you will be using it only for debug purposes. In other cases, you
should modify package's PKGBUILD file only for each package you would
like to rebuild.
General
As of pacman 4.1, /etc/makepkg.conf has debug compilation flags in
DEBUG_CFLAGS and DEBUG_CXXFLAGS. To use them, enable the debug makepkg
option, and disable strip.
OPTIONS+=(debug !strip)
These settings will force compilation with debugging information and
will disable the stripping of executables. (If you do not disable strip,
debugging information will be generated anyway, but moved to a separate
foo-debug package).
To apply this setting to a single package, modify the PKGBUILD:
options=(debug !strip)" -
https://wiki.archlinux.org/index.php/Debug_-_Getting_Traces#PKGBUILD
[rocketmouse archlinux ~]$ ls -hAl /var/abs/extra/evolution*
/var/abs/extra/evolution:
total 8.0K
-rw-r--r-- 1 root root 346 Dec 13 00:05 evolution.install
-rw-r--r-- 1 root root 2.8K Dec 13 00:05 PKGBUILD
/var/abs/extra/evolution-data-server:
total 8.0K
-rw-r--r-- 1 root root 148 Dec 13 00:05 evolution-data-server.install
-rw-r--r-- 1 root root 1.3K Dec 13 00:05 PKGBUILD
/var/abs/extra/evolution-ews:
total 4.0K
-rw-r--r-- 1 root root 841 Dec 13 00:05 PKGBUILD
[rocketmouse archlinux ~]$ grep
options /var/abs/extra/evolution/PKGBUILD
options=('!emptydirs')
Replace it with options options=(debug !strip) and build the package.
Hth,
Ralf
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]