Opened 11 months ago

Closed 4 months ago

#12797 closed defect (fixed)

Debug with gdb - no debugging symbols found

Reported by: toby63 Owned by: toby63
Priority: normal Component: Ports
Version: Keywords:
Cc: Game:

Description

I tried to debug "The longest Journey" because of ticket 12762.

Now every time I try to run:

gdb scummvm

It shows me:

Reading symbols from scummvm...
(No debugging symbols found in scummvm)

I used the following config for compilation:

  ./configure \
    --enable-c++11 \
    --disable-all-engines \
    --enable-engine=stark,sword25 \
    --prefix=/usr

System info:
OS: Arch Linux
GDB version: GNU gdb (GDB) 10.2

Change History (5)

comment:1 by sev-, 11 months ago

Do you have -g option in CXXFLAGS in the generated config.mk file after you run configure?

comment:2 by sev-, 11 months ago

Component: --Unset--Ports

comment:3 by toby63, 11 months ago

Yes:

CXXFLAGS := -march=x86-64 -mtune=generic -O2 -pipe -fno-plt -fexceptions         -Wp,-D_FORTIFY_SOURCE=2 -Wformat -Werror=format-security         -fstack-clash-protection -fcf-protection -Wp,-D_GLIBCXX_ASSERTIONS  -W -Wno-unused-parameter -Wno-empty-body -fno-operator-names -std=c++11 -g -fvar-tracking-assignments -pedantic -Wno-long-long   -I/usr/include/gtk-3.0 -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/harfbuzz -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/fribidi -I/usr/include/cairo -I/usr/include/lzo -I/usr/include/pixman-1 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/gio-unix-2.0 -I/usr/include/cloudproviders -I/usr/include/atk-1.0 -I/usr/include/at-spi2-atk/2.0 -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/usr/include/at-spi-2.0 -pthread  -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/harfbuzz -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include

comment:4 by sev-, 7 months ago

This is weird, it was working sinceforever. I use debugger very often, sometimes daily. It must be something in your setup. Do you happen to see a STRIP command as the final step after LINK?

Also, run configure with --enable-verbose-build, build the whole thing, after that, remove any *.o file, run make again and paste the full output here. E.g. the output will be consisting of compiling one file, AR/RANLIB one library and final step on linking ScummVM, but all the command line parameters will be visible.

in reply to:  4 comment:5 by toby63, 4 months ago

Owner: set to toby63
Resolution: fixed
Status: newclosed

Replying to sev-:

This is weird, it was working sinceforever. I use debugger very often, sometimes daily. It must be something in your setup. Do you happen to see a STRIP command as the final step after LINK?

Also, run configure with --enable-verbose-build, build the whole thing, after that, remove any *.o file, run make again and paste the full output here. E.g. the output will be consisting of compiling one file, AR/RANLIB one library and final step on linking ScummVM, but all the command line parameters will be visible.

Sry for the late answer, I just checked old emails and found one about this comment.
I guess you are right, I used the Arch Build System and it seems that this usually strips out all debugging symbols (IIRC).
So this is probably the explanation.

Note: See TracTickets for help on using tickets.