Re: gdb: No symbol table info available

2017-12-10 Thread Mark Wielaard
On Sun, 2017-12-10 at 14:10 +0100, Jan Kratochvil wrote: > the debuginfo-install command installs only *-debuginfo and not the > *-debugsource counterpart which is then missing for GDB.  That is now > a DNF bug I guess. It is indeed: https://bugzilla.redhat.com/show_bug.cgi?id=1494628 There is a

Re: gdb: No symbol table info available

2017-12-10 Thread Jan Kratochvil
On Sun, 10 Dec 2017 13:43:25 +0100, Richard Shaw wrote: > I pretty much did the same thing with valgrind but the output of your > script is much more concise and easier to read. Fedora GDB should print the dnf debuginfo-install command. When it does not? It uses a similar script logic internally.

Re: gdb: No symbol table info available

2017-12-10 Thread Richard Shaw
On Sat, Dec 9, 2017 at 5:49 PM, Ian Kent wrote: > eu-unstrip -n --core coredump |\ > gawk '{TMP=$2; $1=$2=""; print "/usr/lib/debug/.build-id/" > substr(TMP,0,2) "/" substr(TMP,3,38) $0}' > > Using the output from above dnf can be used to work out what's missing > with somewhat less guess wor

Re: gdb: No symbol table info available

2017-12-10 Thread Richard Shaw
On Sat, Dec 9, 2017 at 5:49 PM, Ian Kent wrote: > On 10/12/17 02:13, Richard Shaw wrote: > > I'm working on a segfault in the latest version of hedgewars and I can > reproduce the crash easy enough and I have installed both the debuginfo for > hedgewars and all the packages gdb suggested but the

Re: gdb: No symbol table info available

2017-12-10 Thread Richard Shaw
On Sat, Dec 9, 2017 at 2:11 PM, John Reiser wrote: > I'm working on a segfault in the latest version of hedgewars and I can >> reproduce the crash easy enough ... >> > > Filing a bugzilla report and including a reproducible test case > enables others to help you. https://bugzilla.redhat.com I

Re: gdb: No symbol table info available

2017-12-09 Thread Ian Kent
On 10/12/17 02:13, Richard Shaw wrote: > I'm working on a segfault in the latest version of hedgewars and I can > reproduce the crash easy enough and I have installed both the debuginfo for > hedgewars and all the packages gdb suggested but the end of the log[1] still > says: Getting all the de

Re: gdb: No symbol table info available

2017-12-09 Thread John Reiser
I'm working on a segfault in the latest version of hedgewars and I can reproduce the crash easy enough ... Filing a bugzilla report and including a reproducible test case enables others to help you. https://bugzilla.redhat.com ___ devel mailing list

Re: gdb: No symbol table info available

2017-12-09 Thread Jan Kratochvil
On Sat, 09 Dec 2017 20:42:46 +0100, Richard Shaw wrote: > Any tips? A correct backtrace would have replaced your line #10 0x in ?? () with line #10 0x0040043a in _start () but otherwise everything would be all the same. Tips in general for segfaults are valgrind. Or bet

Re: gdb: No symbol table info available

2017-12-09 Thread Richard Shaw
On Sat, Dec 9, 2017 at 1:29 PM, Jan Kratochvil wrote: > On Sat, 09 Dec 2017 19:13:24 +0100, Richard Shaw wrote: > > #9 0x7621f891 in __libc_start_main (main=0x0, argc=0, argv=0x0, > > init=, fini=, rtld_fini=, > > stack_end=0x0) at ../csu/libc-start.c:329 > > result = > >

Re: gdb: No symbol table info available

2017-12-09 Thread Jan Kratochvil
On Sat, 09 Dec 2017 19:13:24 +0100, Richard Shaw wrote: > #9 0x7621f891 in __libc_start_main (main=0x0, argc=0, argv=0x0, > init=, fini=, rtld_fini=, > stack_end=0x0) at ../csu/libc-start.c:329 > result = > unwind_buf = {cancel_jmp_buf = {{jmp_buf = {4309931, 0, 421711

gdb: No symbol table info available

2017-12-09 Thread Richard Shaw
I'm working on a segfault in the latest version of hedgewars and I can reproduce the crash easy enough and I have installed both the debuginfo for hedgewars and all the packages gdb suggested but the end of the log[1] still says: No symbol table info available. Any ideas? Thanks Richard [1] $ c