AOA Forums AOA Forums AOA Forums Folding For Team 45 AOA Files Home Front Page Become an AOA Subscriber! UserCP Calendar Memberlist FAQ Search Forum Home


Go Back   AOA Forums > Software > OS, Software, Firmware, and BIOS > Linux

Linux Questions and information concerning Linux


Reply
 
LinkBack Thread Tools Rate Thread
  #1 (permalink)  
Old 15th November, 2010, 04:40 PM
ThunderRd's Avatar
Irreverent Query Chairman
 
Join Date: June 2007
Location: NYC native in northern Thailand
Posts: 2,241

How to produce backtrace/stacktrace in Gentoo

On one of my machines I have come across an unusual bug in compiz and one of the devs on IRC has asked me to give him some debugging.

I did a little research and have come up with the following:
CFLAGS="-march=opteron -O0 -pipe -ggdb"
CXXFLAGS="${CFLAGS}"
FEATURES="splitdebug"

Then I recompiled glibc, and all of the related compiz packages.

I can reproduce the bug at will. What's the proper way to provide him with the debugging information? I didn't want to ask him to teach me on IRC. Those guys keep pretty busy over there.

He also suggested that it would be good to emerge valgrind and provide him with the output of running compiz within valgrind. It looks like I should just run: 'valgrind -v <my_package_here+arguments>'

But I can't figure out how to pipe the output, and to where. Anybody know how?


EDIT: found this page: http://www.gentoo.org/proj/en/qa/backtraces.xml

Is there anything I should be warned about?
__________________
#1: Tt Armor, ASUS Maximus Extreme, QX9650@4.1G, 8G Corsair Dominator GT DDR3-2000, Corsair HX1050, H2O-Swiftech, Gigabyte GTX470/Arctic Accelero Xtreme Plus II, Intel 520 SSD, Kingston SSD, 2xRaptor 150G RAID0, Win 7 Pro 64
#2: Tt Shark, ASUS P5Q Pro Turbo, Q6600@3.8G, 4G HyperX-1600, Corsair HX850, CoolerMaster V10, 2xASUS 9600GT, 2xRaptor 74G RAID0, OCZ Vertex 4 SSD, Gentoo/siduction Linux [64-bit]
#3, #4: Opteron 170@2.75G nude, A8N-SLI Deluxe, Gentoo

AOA Folding @HomeOur sister site: www.gamersonlinux.com

Last edited by ThunderRd; 16th November, 2010 at 03:13 AM.
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
  #2 (permalink)  
Old 17th November, 2010, 04:32 AM
Gizmo's Avatar
Chief BBS Administrator
BassTeroids Champion, Global Player Champion, Aim & Fire Champion, Puzzle Maniax Champion, Othello Champion, Canyon Glider Champion, Unicycle Challenge Champion, YetiSports 9: Final Spit Champion, Zed Champion
 
Join Date: May 2003
Location: Webb City, Mo
Posts: 16,178
Send a message via ICQ to Gizmo Send a message via AIM to Gizmo Send a message via MSN to Gizmo Send a message via Yahoo to Gizmo Send a message via Skype™ to Gizmo

Ah, I was just getting ready to post the Gentoo link and read the rest of your message and saw that you had found it.

As far as warnings, there's nothning that immediately comes to mind.
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
  #3 (permalink)  
Old 17th November, 2010, 03:54 PM
ThunderRd's Avatar
Irreverent Query Chairman
 
Join Date: June 2007
Location: NYC native in northern Thailand
Posts: 2,241

This is the output I get from gdb. I'm not sure if it is useful or not. Why are there messages about no debug symbols? Have I missed a step?


Code:
thunderrd@OPTERON-185:~$ gdb compiz
GNU gdb (Gentoo 7.2 p1) 7.2
Copyright (C) 2010 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-pc-linux-gnu".
For bug reporting instructions, please see:
<http://bugs.gentoo.org/>...
Reading symbols from /usr/bin/compiz...(no debugging symbols found)...done.
(gdb) set args --replace ccp&
(gdb) run
Starting program: /usr/bin/compiz --replace ccp&
During startup program exited normally.
(gdb) Backend     : ini
Integration : true
Profile     : default
Adding plugins
Initializing core options...done
Initializing composite options...done
Initializing opengl options...done
Initializing crashhandler options...done
Initializing move options...done
Initializing cube options...done
/usr/bin/compiz (core) - Warn: Value type is not yet set
/usr/bin/compiz (core) - Warn: Value type is not yet set
Initializing rotate options...done
Initializing splash options...done
Setting Update "start_wm"
Setting Update "wm_cmd"
Setting Update "acceleration"
Setting Update "speed"
Setting Update "timestep"
Setting Update "skydome"
Setting Update "skydome_image"
Setting Update "skydome_animated"
Setting Update "skydome_gradient_start_color"
Setting Update "skydome_gradient_end_color"
Setting Update "active_opacity"
Setting Update "zoom"
Setting Update "speed"
Setting Update "timestep"
Setting Update "background"
Setting Update "logo"
Reading symbols from /usr/bin/compiz...(no debugging symbols found)...done.
Attaching to program: /usr/bin/compiz, process 2042
Reading symbols from /usr/lib/libX11.so.6...(no debugging symbols found)...done.
Loaded symbols for /usr/lib/libX11.so.6
Reading symbols from /usr/lib/libXrandr.so.2...(no debugging symbols found)...done.
Loaded symbols for /usr/lib/libXrandr.so.2
Reading symbols from /usr/lib/libXinerama.so.1...(no debugging symbols found)...done.
Loaded symbols for /usr/lib/libXinerama.so.1
Reading symbols from /usr/lib/libXext.so.6...(no debugging symbols found)...done.
Loaded symbols for /usr/lib/libXext.so.6
Reading symbols from /usr/lib/libSM.so.6...(no debugging symbols found)...done.
Loaded symbols for /usr/lib/libSM.so.6
Reading symbols from /usr/lib/libICE.so.6...(no debugging symbols found)...done.
Loaded symbols for /usr/lib/libICE.so.6
Reading symbols from /usr/lib/libstartup-notification-1.so.0...(no debugging symbols found)...done.
Loaded symbols for /usr/lib/libstartup-notification-1.so.0
Reading symbols from /lib/libpthread.so.0...Reading symbols from /usr/lib64/debug/lib64/libpthread-2.12.1.so.debug...done.
[Thread debugging using libthread_db enabled]
done.
Loaded symbols for /lib/libpthread.so.0
Reading symbols from /lib/libdl.so.2...Reading symbols from /usr/lib64/debug/lib64/libdl-2.12.1.so.debug...done.
done.
Loaded symbols for /lib/libdl.so.2
Reading symbols from /usr/lib/gcc/x86_64-pc-linux-gnu/4.4.5/libstdc++.so.6...(no debugging symbols found)...done.
Loaded symbols for /usr/lib/gcc/x86_64-pc-linux-gnu/4.4.5/libstdc++.so.6
Reading symbols from /lib/libgcc_s.so.1...(no debugging symbols found)...done.
Loaded symbols for /lib/libgcc_s.so.1
Reading symbols from /lib/libc.so.6...Reading symbols from /usr/lib64/debug/lib64/libc-2.12.1.so.debug...done.
done.
Loaded symbols for /lib/libc.so.6
Reading symbols from /usr/lib/libxcb.so.1...(no debugging symbols found)...done.
Loaded symbols for /usr/lib/libxcb.so.1
Reading symbols from /usr/lib/libXrender.so.1...(no debugging symbols found)...done.
Loaded symbols for /usr/lib/libXrender.so.1
Reading symbols from /lib/libuuid.so.1...(no debugging symbols found)...done.
Loaded symbols for /lib/libuuid.so.1
Reading symbols from /usr/lib/libxcb-aux.so.0...(no debugging symbols found)...done.
Loaded symbols for /usr/lib/libxcb-aux.so.0
Reading symbols from /usr/lib/libxcb-atom.so.1...(no debugging symbols found)...done.
Loaded symbols for /usr/lib/libxcb-atom.so.1
Reading symbols from /lib64/ld-linux-x86-64.so.2...Reading symbols from /usr/lib64/debug/lib64/ld-2.12.1.so.debug...done.
done.
Loaded symbols for /lib64/ld-linux-x86-64.so.2
Reading symbols from /lib/libm.so.6...Reading symbols from /usr/lib64/debug/lib64/libm-2.12.1.so.debug...done.
done.
Loaded symbols for /lib/libm.so.6
Reading symbols from /usr/lib/libXau.so.6...(no debugging symbols found)...done.
Loaded symbols for /usr/lib/libXau.so.6
Reading symbols from /usr/lib/libXdmcp.so.6...(no debugging symbols found)...done.
Loaded symbols for /usr/lib/libXdmcp.so.6
Reading symbols from /usr/lib/libXcursor.so.1...(no debugging symbols found)...done.
Loaded symbols for /usr/lib/libXcursor.so.1
Reading symbols from /usr/lib/libXfixes.so.3...(no debugging symbols found)...done.
Loaded symbols for /usr/lib/libXfixes.so.3
Reading symbols from /usr/lib64/compiz/libccp.so...Reading symbols from /usr/lib64/debug/usr/lib64/compiz/libccp.so.debug...done.
done.
Loaded symbols for /usr/lib64/compiz/libccp.so
Reading symbols from /usr/lib64/libcompizconfig.so.0...Reading symbols from /usr/lib64/debug/usr/lib64/libcompizconfig.so.0.0.0.debug...done.
done.
Loaded symbols for /usr/lib64/libcompizconfig.so.0
Reading symbols from /usr/lib/libxml2.so.2...(no debugging symbols found)...done.
Loaded symbols for /usr/lib/libxml2.so.2
Reading symbols from /usr/lib/libprotobuf.so.6...(no debugging symbols found)...done.
Loaded symbols for /usr/lib/libprotobuf.so.6
Reading symbols from /lib/libz.so.1...(no debugging symbols found)...done.
Loaded symbols for /lib/libz.so.1
Reading symbols from /usr/lib64/compizconfig/32	../sysdeps/unix/sysv/linux/waitpid.c: No such file or directory.
backends/libini.so...Reading symbols from /usr/lib64/debug/usr/lib64/compizconfig/backends/libini.so.debug...done.
done.
Loaded symbols for /usr/lib64/compizconfig/backends/libini.so
Reading symbols from /usr/lib64/compiz/libcomposite.so...(no debugging symbols found)...done.
Loaded symbols for /usr/lib64/compiz/libcomposite.so
Reading symbols from /usr/lib/libXdamage.so.1...(no debugging symbols found)...done.
Loaded symbols for /usr/lib/libXdamage.so.1
Reading symbols from /usr/lib/libXcomposite.so.1...(no debugging symbols found)...done.
Loaded symbols for /usr/lib/libXcomposite.so.1
Reading symbols from /usr/lib64/compiz/libopengl.so...(no debugging symbols found)...done.
Loaded symbols for /usr/lib64/compiz/libopengl.so
Reading symbols from //usr/lib64/opengl/nvidia/lib/libGL.so.1...(no debugging symbols found)...done.
Loaded symbols for //usr/lib64/opengl/nvidia/lib/libGL.so.1
Reading symbols from //usr/lib64/opengl/nvidia/lib/libnvidia-tls.so.260.19.12...(no debugging symbols found)...done.
Loaded symbols for //usr/lib64/opengl/nvidia/lib/libnvidia-tls.so.260.19.12
Reading symbols from /usr/lib/libnvidia-glcore.so.260.19.12...(no debugging symbols found)...done.
Loaded symbols for /usr/lib/libnvidia-glcore.so.260.19.12
Reading symbols from /usr/lib64/compiz/libcrashhandler.so...Reading symbols from /usr/lib64/debug/usr/lib64/compiz/libcrashhandler.so.debug...(no debugging symbols found)...done.
(no debugging symbols found)...done.
Loaded symbols for /usr/lib64/compiz/libcrashhandler.so
Reading symbols from /usr/lib64/compiz/libimgpng.so...(no debugging symbols found)...done.
Loaded symbols for /usr/lib64/compiz/libimgpng.so
Reading symbols from /usr/lib/libpng14.so.14...(no debugging symbols found)...done.
Loaded symbols for /usr/lib/libpng14.so.14
Reading symbols from /usr/lib64/compiz/libmove.so...(no debugging symbols found)...done.
Loaded symbols for /usr/lib64/compiz/libmove.so
Reading symbols from /usr/lib64/compiz/libcube.so...(no debugging symbols found)...done.
Loaded symbols for /usr/lib64/compiz/libcube.so
Reading symbols from /usr/lib64/compiz/libregex.so...(no debugging symbols found)...done.
Loaded symbols for /usr/lib64/compiz/libregex.so
Reading symbols from /usr/lib64/compiz/librotate.so...(no debugging symbols found)...done.
Loaded symbols for /usr/lib64/compiz/librotate.so
Reading symbols from /usr/lib64/compiz/libsplash.so...Reading symbols from /usr/lib64/debug/usr/lib64/compiz/libsplash.so.debug...(no debugging symbols found)...done.
(no debugging symbols found)...done.
Loaded symbols for /usr/lib64/compiz/libsplash.so
0x00007ffff622fa6e in __libc_waitpid (pid=<value optimized out>, stat_loc=0x7fffffffcecc, options=<value optimized out>) at ../sysdeps/unix/sysv/linux/waitpid.c:32
	in ../sysdeps/unix/sysv/linux/waitpid.c
(gdb) 
Thread 1 (Thread 0x7ffff7fd0760 (LWP 2042)):
#0  0x00007ffff622fa6e in __libc_waitpid (pid=<value optimized out>, stat_loc=0x7fffffffcecc, options=<value optimized out>) at ../sysdeps/unix/sysv/linux/waitpid.c:32
        oldtype = <value optimized out>
        result = <value optimized out>
#1  0x00007ffff61caef9 in do_system (line=<value optimized out>) at ../sysdeps/posix/system.c:149
        __result = -512
        _buffer = {__routine = 0x7ffff61cb250 <cancel_handler>, __arg = 0x7fffffffcec8, __canceltype = 0, __prev = 0x0}
        _avail = 1
        status = <value optimized out>
        save = <value optimized out>
        pid = 2043
        sa = {__sigaction_handler = {sa_handler = 0x1, sa_sigaction = 0x1}, sa_mask = {__val = {65536, 0 <repeats 15 times>}}, sa_flags = 0, sa_restorer = 0x7ffff6195148}
        omask = {__val = {1024, 4294967295, 206158430256, 1, 2195512, 0, 8999496, 0, 140737333305344, 140737351952082, 1, 0, 12884903930, 140737322242376, 140737488343856, 2042}}
#2  0x00007ffff0ae7683 in crash_handler(int) () from /usr/lib64/compiz/libcrashhandler.so
#3  <signal handler called>
#4  0x00007fffef9af9ef in SplashScreen::preparePaint(int) () from /usr/lib64/compiz/libsplash.so
#5  0x00007ffff3bb93f1 in CompositeScreen::preparePaint(int) () from /usr/lib64/compiz/libcomposite.so
#6  0x00007ffff3bb89b8 in CompositeScreen::handlePaintTimeout() () from /usr/lib64/compiz/libcomposite.so
#7  0x00007ffff3bbec77 in boost::_mfi::mf0<bool, CompositeScreen>::operator()(CompositeScreen*) const () from /usr/lib64/compiz/libcomposite.so
#8  0x00007ffff3bbe8d5 in bool boost::_bi::list1<boost::_bi::value<CompositeScreen*> >::operator()<bool, boost::_mfi::mf0<bool, CompositeScreen>, boost::_bi::list0>(boost::_bi::type<bool>, boost::_mfi::mf0<bool, CompositeScreen>&, boost::_bi::list0&, long) () from /usr/lib64/compiz/libcomposite.so
#9  0x00007ffff3bbe3d7 in boost::_bi::bind_t<bool, boost::_mfi::mf0<bool, CompositeScreen>, boost::_bi::list1<boost::_bi::value<CompositeScreen*> > >::operator()() () from /usr/lib64/compiz/libcomposite.so
#10 0x00007ffff3bbdd2f in boost::detail::function::function_obj_invoker0<boost::_bi::bind_t<bool, boost::_mfi::mf0<bool, CompositeScreen>, boost::_bi::list1<boost::_bi::value<CompositeScreen*> > >, bool>::invoke(boost::detail::function::function_buffer&) () from /usr/lib64/compiz/libcomposite.so
#11 0x000000000047ba4b in boost::function0<bool>::operator()() const ()
#12 0x0000000000465cfe in PrivateScreen::handleTimers(timeval*) ()
#13 0x0000000000464ea5 in CompScreen::eventLoop() ()
#14 0x0000000000461bf2 in main ()


#0  0x00007ffff622fa6e in __libc_waitpid (pid=<value optimized out>, stat_loc=0x7fffffffcecc, options=<value optimized out>) at ../sysdeps/unix/sysv/linux/waitpid.c:32
#1  0x00007ffff61caef9 in do_system (line=<value optimized out>) at ../sysdeps/posix/system.c:149
#2  0x00007ffff0ae7683 in crash_handler(int) () from /usr/lib64/compiz/libcrashhandler.so
#3  <signal handler called>
#4  0x00007fffef9af9ef in SplashScreen::preparePaint(int) () from /usr/lib64/compiz/libsplash.so
#5  0x00007ffff3bb93f1 in CompositeScreen::preparePaint(int) () from /usr/lib64/compiz/libcomposite.so
#6  0x00007ffff3bb89b8 in CompositeScreen::handlePaintTimeout() () from /usr/lib64/compiz/libcomposite.so
#7  0x00007ffff3bbec77 in boost::_mfi::mf0<bool, CompositeScreen>::operator()(CompositeScreen*) const () from /usr/lib64/compiz/libcomposite.so
#8  0x00007ffff3bbe8d5 in bool boost::_bi::list1<boost::_bi::value<CompositeScreen*> >::operator()<bool, boost::_mfi::mf0<bool, CompositeScreen>, boost::_bi::list0>(boost::_bi::type<bool>, boost::_mfi::mf0<bool, CompositeScreen>&, boost::_bi::list0&, long) () from /usr/lib64/compiz/libcomposite.so
#9  0x00007ffff3bbe3d7 in boost::_bi::bind_t<bool, boost::_mfi::mf0<bool, CompositeScreen>, boost::_bi::list1<boost::_bi::value<CompositeScreen*> > >::operator()() () from /usr/lib64/compiz/libcomposite.so
#10 0x00007ffff3bbdd2f in boost::detail::function::function_obj_invoker0<boost::_bi::bind_t<bool, boost::_mfi::mf0<bool, CompositeScreen>, boost::_bi::list1<boost::_bi::value<CompositeScreen*> > >, bool>::invoke(boost::detail::function::function_buffer&) () from /usr/lib64/compiz/libcomposite.so
#11 0x000000000047ba4b in boost::function0<bool>::operator()() const ()
#12 0x0000000000465cfe in PrivateScreen::handleTimers(timeval*) ()
#13 0x0000000000464ea5 in CompScreen::eventLoop() ()
#14 0x0000000000461bf2 in main ()
A debugging session is active.

	Inferior 1 [process 2042] will be detached.

Quit anyway? (y or n) [answered Y; input not from terminal]
Detaching from program: /usr/bin/compiz, process 2042

[CRASH_HANDLER]: "/tmp/compiz_crash-2042.out" created!


(xfwm4:2051): xfconf-WARNING **: Error check failed at IA__xfconf_channel_has_property():639: Property "/general/margin_bottom" does not exist on channel "xfwm4"

(xfwm4:2051): xfconf-WARNING **: Error check failed at IA__xfconf_channel_has_property():639: Property "/general/margin_left" does not exist on channel "xfwm4"

(xfwm4:2051): xfconf-WARNING **: Error check failed at IA__xfconf_channel_has_property():639: Property "/general/margin_right" does not exist on channel "xfwm4"

(xfwm4:2051): xfconf-WARNING **: Error check failed at IA__xfconf_channel_has_property():639: Property "/general/margin_top" does not exist on channel "xfwm4"
__________________
#1: Tt Armor, ASUS Maximus Extreme, QX9650@4.1G, 8G Corsair Dominator GT DDR3-2000, Corsair HX1050, H2O-Swiftech, Gigabyte GTX470/Arctic Accelero Xtreme Plus II, Intel 520 SSD, Kingston SSD, 2xRaptor 150G RAID0, Win 7 Pro 64
#2: Tt Shark, ASUS P5Q Pro Turbo, Q6600@3.8G, 4G HyperX-1600, Corsair HX850, CoolerMaster V10, 2xASUS 9600GT, 2xRaptor 74G RAID0, OCZ Vertex 4 SSD, Gentoo/siduction Linux [64-bit]
#3, #4: Opteron 170@2.75G nude, A8N-SLI Deluxe, Gentoo

AOA Folding @HomeOur sister site: www.gamersonlinux.com
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
  #4 (permalink)  
Old 17th November, 2010, 07:14 PM
Gizmo's Avatar
Chief BBS Administrator
BassTeroids Champion, Global Player Champion, Aim & Fire Champion, Puzzle Maniax Champion, Othello Champion, Canyon Glider Champion, Unicycle Challenge Champion, YetiSports 9: Final Spit Champion, Zed Champion
 
Join Date: May 2003
Location: Webb City, Mo
Posts: 16,178
Send a message via ICQ to Gizmo Send a message via AIM to Gizmo Send a message via MSN to Gizmo Send a message via Yahoo to Gizmo Send a message via Skype™ to Gizmo

Most of those warnings are from X libraries which you didn't recompile in debug mode. That probably doesn't matter. Interestingly, one of the warnings is coming from the compiz executable itself, though. Are you sure you recompiled compiz with debugging info?

In any case, once you get all the debugging info, I <THINK> the /tmp/compiz-crash-2042.out is what they are going to need.
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
  #5 (permalink)  
Old 18th November, 2010, 02:16 PM
ThunderRd's Avatar
Irreverent Query Chairman
 
Join Date: June 2007
Location: NYC native in northern Thailand
Posts: 2,241

Quote:
Originally Posted by Gizmo View Post
Are you sure you recompiled compiz with debugging info?
I re-compiled compiz (and its related packages) with the flags in my first post. Should that not have provided the debug symbols?

compiz-crash-2042.out does not provide a backtrace. That's why he asked me for the debug info.
__________________
#1: Tt Armor, ASUS Maximus Extreme, QX9650@4.1G, 8G Corsair Dominator GT DDR3-2000, Corsair HX1050, H2O-Swiftech, Gigabyte GTX470/Arctic Accelero Xtreme Plus II, Intel 520 SSD, Kingston SSD, 2xRaptor 150G RAID0, Win 7 Pro 64
#2: Tt Shark, ASUS P5Q Pro Turbo, Q6600@3.8G, 4G HyperX-1600, Corsair HX850, CoolerMaster V10, 2xASUS 9600GT, 2xRaptor 74G RAID0, OCZ Vertex 4 SSD, Gentoo/siduction Linux [64-bit]
#3, #4: Opteron 170@2.75G nude, A8N-SLI Deluxe, Gentoo

AOA Folding @HomeOur sister site: www.gamersonlinux.com
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
  #6 (permalink)  
Old 19th November, 2010, 12:45 AM
Gizmo's Avatar
Chief BBS Administrator
BassTeroids Champion, Global Player Champion, Aim & Fire Champion, Puzzle Maniax Champion, Othello Champion, Canyon Glider Champion, Unicycle Challenge Champion, YetiSports 9: Final Spit Champion, Zed Champion
 
Join Date: May 2003
Location: Webb City, Mo
Posts: 16,178
Send a message via ICQ to Gizmo Send a message via AIM to Gizmo Send a message via MSN to Gizmo Send a message via Yahoo to Gizmo Send a message via Skype™ to Gizmo

I've not attempted to generate a crash dump before, as I've always debugged right from within gdb, but if you've got the debug symbols in there then the compiz-crash-2042.out file SHOULD contain the same info as your output above, I would think.

Sorry to not be of more help. You might be able to pastebin him the output from gdb.

Do:
Code:
equery belongs /usr/bin/compiz
That will tell you what package that file belongs to, and you can verify that you recompiled that package with the debugging symbols. If you did, and you're still getting the notice that compiz does not have debugging symbols, then I'm stumped.
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
  #7 (permalink)  
Old 19th November, 2010, 04:27 PM
ThunderRd's Avatar
Irreverent Query Chairman
 
Join Date: June 2007
Location: NYC native in northern Thailand
Posts: 2,241

OK, I've talked to the dev again. He is not a gentoo user, but told me that FEATURES="splitdebug" may mess with the "line numbers". I still am not clear on what exactly the line numbers are, and he was busy.

He also said that gcc versions after 4.4.3 have been unreliable compiling compiz. My version is 4.4.5-something.

So I masked >=4.4.4 and downgraded gcc to 4.4.3.

Then I did some research, and changed the FEATURES="splitdebug" to "nostrip". AFAICT this will prevent any stripping of the binaries, and will provide the most information. I recompiled everything - glibc, gcc itself, and all of the compiz packages. Then I crashed compiz again.

I showed him the new backtrace. He still doesn't see the line numbers, so I don't know what to do to produce them.

What exactly are these line numbers, and what do I have to do to include them in the debugging information? My next step is to re-compile again, like this:

Code:
USE="debug" emerge -v glibc gdb compiz compiz-fusion etc etc...
and see where that gets me.

Here is the latest information. It matches the crash.out file, the way you said it would: http://pastebin.com/gJFBHkAe
__________________
#1: Tt Armor, ASUS Maximus Extreme, QX9650@4.1G, 8G Corsair Dominator GT DDR3-2000, Corsair HX1050, H2O-Swiftech, Gigabyte GTX470/Arctic Accelero Xtreme Plus II, Intel 520 SSD, Kingston SSD, 2xRaptor 150G RAID0, Win 7 Pro 64
#2: Tt Shark, ASUS P5Q Pro Turbo, Q6600@3.8G, 4G HyperX-1600, Corsair HX850, CoolerMaster V10, 2xASUS 9600GT, 2xRaptor 74G RAID0, OCZ Vertex 4 SSD, Gentoo/siduction Linux [64-bit]
#3, #4: Opteron 170@2.75G nude, A8N-SLI Deluxe, Gentoo

AOA Folding @HomeOur sister site: www.gamersonlinux.com

Last edited by ThunderRd; 19th November, 2010 at 04:55 PM.
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
  #8 (permalink)  
Old 19th November, 2010, 06:51 PM
Gizmo's Avatar
Chief BBS Administrator
BassTeroids Champion, Global Player Champion, Aim & Fire Champion, Puzzle Maniax Champion, Othello Champion, Canyon Glider Champion, Unicycle Challenge Champion, YetiSports 9: Final Spit Champion, Zed Champion
 
Join Date: May 2003
Location: Webb City, Mo
Posts: 16,178
Send a message via ICQ to Gizmo Send a message via AIM to Gizmo Send a message via MSN to Gizmo Send a message via Yahoo to Gizmo Send a message via Skype™ to Gizmo

USE="debug" probably won't make any difference, and is not the preferred way to generate debugging info anyway. The Gentoo devs prefer for packages not to use that flag, as it's intended primarily for debugging ebuilds, not applications, IIRC.

As for the line numbers, that would be the exact point in the source code where the crash occurred: gdb will provide the actual line number and source file of the location of the crash if it has the relevant info. However, for that to happen, two things are required:

1. The application must be compiled with debugging information (I'm still mystified why gdb indicates that compiz is being loaded without debugging symbols)
2. You have to be running the debugger within the source tree for the application.

As an example, I recently debugged the mount utility. In order to debug it, I had to run
Code:
ebuild /usr/portage/sys-apps/util-linux-2.18-r1.ebuild compile
which extracted the source tarball into /var/tmp/portage and then applied all the relevant patches and compiled the code. Then I had to cd to the directory containing the source files I was interested in and actually run the application under the debugger, while in that source directory.
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
  #9 (permalink)  
Old 19th November, 2010, 07:21 PM
ThunderRd's Avatar
Irreverent Query Chairman
 
Join Date: June 2007
Location: NYC native in northern Thailand
Posts: 2,241

I tried running compiz within gdb:
Code:
OPTERON-185 ~ #gdb /usr/bin/compiz
(gdb)set args --replace ccp
(gdb)run
and got the same result, but I wasn't in the source directory. I'll have to boot to that test install tomorrow and try to run it the way you say. But where would that be? I only know where the executable is, in /usr/bin. Where does the source reside when we emerge a package? Is it /usr/portage? Or do we not have the source when it comes from an ebuild?
__________________
#1: Tt Armor, ASUS Maximus Extreme, QX9650@4.1G, 8G Corsair Dominator GT DDR3-2000, Corsair HX1050, H2O-Swiftech, Gigabyte GTX470/Arctic Accelero Xtreme Plus II, Intel 520 SSD, Kingston SSD, 2xRaptor 150G RAID0, Win 7 Pro 64
#2: Tt Shark, ASUS P5Q Pro Turbo, Q6600@3.8G, 4G HyperX-1600, Corsair HX850, CoolerMaster V10, 2xASUS 9600GT, 2xRaptor 74G RAID0, OCZ Vertex 4 SSD, Gentoo/siduction Linux [64-bit]
#3, #4: Opteron 170@2.75G nude, A8N-SLI Deluxe, Gentoo

AOA Folding @HomeOur sister site: www.gamersonlinux.com

Last edited by ThunderRd; 19th November, 2010 at 07:25 PM.
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
  #10 (permalink)  
Old 19th November, 2010, 07:33 PM
Member
 
Join Date: April 2005
Location: AZ
Posts: 2,446

I'm of no use to you on the problem but,
The source files are stored in /usr/portage/distfiles/
__________________
Biostar TForce X58 - Core i7 920 - 12GB Corsair Dominator DDR3 - EVGA 560ti - PCP&C 750W - Dual boot, Arch Linux/WinXP
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
Reply



Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)
 
Thread Tools
Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On


Similar Threads
Thread Thread Starter Forum Replies Last Post
vlc in gentoo ThunderRd Linux 17 14th October, 2010 07:09 AM
Japanese first to mass-produce ultra-skinny 'safe' lithium battery danrok General Hardware Discussion 5 5th December, 2008 11:04 PM
Algae farm in Mexico to produce ethanol in '09 Daniel ~ Random Nonsense! 0 12th June, 2008 07:12 PM
Computer Produce Blank Screen (urgent) Xcalibur CRASHED! 6 11th July, 2004 07:42 AM
Micirsoft Produce Linux distro Holst Random Nonsense! 6 12th April, 2002 03:24 AM


All times are GMT +1. The time now is 06:08 PM.


Copyright ©2001 - 2010, AOA Forums
Don't Click Here Don't Click Here Either

Search Engine Friendly URLs by vBSEO 3.3.0