Re: [Touch-packages] [Bug 1325503] Re: gdb reports 'corrupt stack' on armhf without symbols

On 17.05.2018 16:03, alamaral wrote: > The problem is that most system library code is built > without -g, so gdb doesn't have whatever information is necessary to > unwind the stack properly. this is wrong. every package is built with -g, however the debug symbols are split out into separate

[Touch-packages] [Bug 1325503] Re: gdb reports 'corrupt stack' on armhf without symbols

Don't know if anyone is still working on this problem (i.e. corrupt stack on arm in gdb), but I've found a solution. Any code that is compiled with -g seems to work fine with gdb, as far as generating a backtrace. The problem is that most system library code is built without -g, so gdb doesn't

[Touch-packages] [Bug 1325503] Re: gdb reports 'corrupt stack' on armhf without symbols

ubuntu-mate (Xenial Xerus) on raspberry pi 3. having similar issue. $ gcc -g main.c -o main $ gdb main GNU gdb (Ubuntu 7.11.1-0ubuntu1~16.04) 7.11.1 Copyright (C) 2016 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later This is free

[Touch-packages] [Bug 1325503] Re: gdb reports 'corrupt stack' on armhf without symbols

Nonny Moose I have the same problem of you (running Ubuntu Mate and gdb v.7.11.1). Actually I can't perform any application in debug due to the same segmentation fault! Did you solve the problem? Thanks Matteo -- You received this bug notification because you are a member of Ubuntu Touch

[Touch-packages] [Bug 1325503] Re: gdb reports 'corrupt stack' on armhf without symbols

I am running Ubuntu Mate Xenial and gdb always reports the following bt, symbols or not: ``` Program received signal SIGSEGV, Segmentation fault. 0x76fd9822 in ?? () from /lib/ld-linux-armhf.so.3 (gdb) bt #0 0x76fd9822 in ?? () from /lib/ld-linux-armhf.so.3 #1 0x76fd983a in ?? () from

[Touch-packages] [Bug 1325503] Re: gdb reports 'corrupt stack' on armhf without symbols

I also see a lot of these errors here on Wily at KDE Plasma: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib/arm-linux-gnueabihf/libthread_db.so.1". __libc_do_syscall () at ../sysdeps/unix/sysv/linux/arm/libc-do-syscall.S:46 [Current thread is 1