On Wed, Apr 11, 2007 at 07:21:53PM +0300, costin c wrote: > On 4/11/07, Daniel Jacobowitz <dan@debian.org> wrote: > >On Wed, Apr 11, 2007 at 06:31:00PM +0300, costin c wrote: > >> Hello > >> > >> How should be used pakages containing debugging symbols/informations, > >> like openoffice.org-dbg > >> When I try to run > >> /usr/lib/debug/usr/lib/openoffice/program/soffice.bin bash show an > >> unexpected error message "cannot execute binary file". > > > >Just install it, don't try to run it. GDB will pick it up > >automatically. > Thank you for answering to my question. > > But running /usr/lib/openoffice/program/soffice.bin under gdb, with > openoffice.org-dbg package installed, doesn't give any additional > information toward running same executable without openoffice.org-dbg > installed. yes it does: isn't the difference in the backtraces obvious to you ? > (gdb) bt > #0 0xb5c99c42 in SalDisplay::Init () from /usr/lib/openoffice/program/libvclplug_gen680li.so > #1 0xb5c9c29e in SalX11Display () from /usr/lib/openoffice/program/libvclplug_gen680li.so > #2 0xb5c8e60d in SalXLib::Init () from /usr/lib/openoffice/program/libvclplug_gen680li.so > #3 0xb5c8f5ee in X11SalData::Init () from /usr/lib/openoffice/program/libvclplug_gen680li.so > #4 0xb5c9eba2 in create_SalInstance () from /usr/lib/openoffice/program/libvclplug_gen680li.so > #5 0xb7eaae32 in tryInstance () from /usr/lib/openoffice/program/libvcl680li.so > #6 0xb7eaaf59 in CreateSalInstance () from /usr/lib/openoffice/program/libvcl680li.so > #7 0xb7c321cd in InitVCL () from /usr/lib/openoffice/program/libvcl680li.so > #8 0xb7c325e1 in ImplSVMain () from /usr/lib/openoffice/program/libvcl680li.so > #9 0xb7c327f5 in SVMain () from /usr/lib/openoffice/program/libvcl680li.so > #10 0x08060be6 in main () > (gdb) bt full > #0 0xb5cd2f48 in SalDisplay::Init () from /usr/lib/openoffice/program/libvclplug_gen680li.so > No symbol table info available. > #1 0xb5cd4200 in SalX11Display::SalX11Display () from /usr/lib/openoffice/program/libvclplug_gen680li.so > No symbol table info available. > #2 0xb5ccad1d in SalXLib::Init () from /usr/lib/openoffice/program/libvclplug_gen680li.so > No symbol table info available. > #3 0xb5cca01b in X11SalData::Init () from /usr/lib/openoffice/program/libvclplug_gen680li.so > No symbol table info available. > #4 0xb5cd5042 in create_SalInstance () from /usr/lib/openoffice/program/libvclplug_gen680li.so > No symbol table info available. > #5 0xb7ee3442 in ?? () from /usr/lib/openoffice/program/libvcl680li.so > No symbol table info available. > #6 0x0809e4b8 in ?? () > No symbol table info available. > #7 0x0809e2e0 in ?? () > No symbol table info available. > #8 0x00000000 in ?? () > No symbol table info available. because it is for me. the very fact that you still have function names without the -dbg is because OOo is C++ and that "thanks to" the C++ symbols names mangling it's able to go back to the real function name if it's an exported symbol. When it's inside the library, then you're doomed (see the frames >= 6 in your backtraces). -- ·O· Pierre Habouzit ··O madcoder@debian.org OOO http://www.madism.org
Attachment:
pgpVfscoMF4H8.pgp
Description: PGP signature