Another crash

[Donald Allen]

On 2/16/07, Ariel <asgnucash at dsgml.com> wrote:
>
>
> On Fri, 16 Feb 2007, Donald Allen wrote:
>
> > so it includes --enable-debug. There are -g switches all over the
> > compilations. But when I start gdb on gnucash, I get the msg "No
> debugging
> > symbols found". And when I actually start the program, I get a bunch
> more of
> > the "No debugging symbols" msgs. Running 'strings' on the executable
> doesn't
> > produce a ton of output that I would expect if symbols were included.
> Any
> > ideas about this?
>
> Often time installers will strip (remove debugging symbols) during
> installation.
>
> Try checking the gnucash binary directly in the build tree. (Run the file
> command on it, it will tell you if it has debugging symbols.)


The gnucash binary in /usr/bin is the only one in the filesystem:

 root at elektra portage # find / -name 'gnucash-bin' -print
/usr/bin/gnucash-bin

This system is built standard gentoo style: two partitions/filesystems, one
small, usually unmounted filesystem containing the boot and grub
directories, and everything else. So if find / didn't find it, it's not
there.

And 'file' confirms that the symbols aren't there (thanks for reminding me
about 'file'):

root at elektra portage # file /usr/bin/gnucash-bin
/usr/bin/gnucash-bin: ELF 32-bit LSB executable, Intel 80386, version 1
(SYSV), for GNU/Linux 2.6.9, dynamically linked (uses shared libs), stripped
root at elektra portage #

I still have the shell output from the build session and it includes this:

strip: i686-pc-linux-gnu-strip --strip-unneeded
   usr/bin/gnucash-bin
   usr/lib/libgncqof.so.1.0.4
   usr/lib/libgncqof-backend-qsf.so

So you are correct. Something else needs to get said to emerge to prevent
this.

/Don

        -Ariel
>