segmentation fault in xfce 4.2.1.1 - gentoo

[Erik Harrison]

On 4/14/05, Robert Kurowski <koorek at o2.pl> wrote:
> On Thu, 14 Apr 2005 11:47:57 +0200
> Jasper Huijsmans <jasper at xfce.org> wrote:
> 
> > And no, this is no a known issue. Could you try and get a backtrace
> from the
> > crash with gdb? In a terminal, when xfce4-panel is not running, type:
> >
> >  $ gdb xfce4-panel
> > gdb> run
> >  [wait for the crash]
> > gdb> bt
> >  [output of backtrace]
> 
> I'm just courius. I see such instructions many times, for Fedora, SuSE,
> Gentoo etc users. So that means packages installed are compiled with
> debug symbols. What's the point in binary packages?

Debug symbols just provide a mapping between human readable names, and
memory addresses. There is no performance overhead to debugging
symbols, except slight startup time increases caused by larger file
sizes.

Binary packages:
 * Install fast, because there is no compiling
 * Can be built explicitly against appropriate dependencies for the OS
 * Often don't have debug symbols ;-)

As you may have noticed, backtraces oftentimes provide no useful info,
because the packagers compiled with debug off. So, we have to ask
"Could you compile again with debug on, and try again?"

Besides this is Gentoo. Unlikely to be a binary package of Xfce.
> 
> If I want to test new software for bugs it's reasonable but somehow
> "stable" software?

All software has bugs. Period. Debugging symbols are most useful when
you have an  unexpected crash - the crash is most unexpected in
"stable" software.

> 
> --
> Robert 'koorek' Kurowski        Jabber: koorek at pld-linux.org
> _______________________________________________
> Xfce mailing list
> Xfce at xfce.org
> http://foo-projects.org/mailman/listinfo/xfce
> http://www.xfce.org
> 


-- 
CAPS LOCK: ITS LIKE THE CRUISE CONTROL FOR AWESOME
-Erik