Re: [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 -dbg

[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 ha

[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 softwar

[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 Bugs, which

[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 /lib/ld-li

[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

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

** Changed in: gdb (Ubuntu) Status: Confirmed => Triaged ** Changed in: gdb (Ubuntu) Importance: Critical => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1325503 Title: gdb reports

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

This may be partially resolved by the reintroduction of the patch in bug 1233185. The initial Stacktrace still ends in a corrupt stack but the non-multiarch version of gdb is able to produce a more useful Stacktrace and a StacktraceAddressSignature when retracing the crash. For example, with the g

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

Hi Maxim, On Wed, Jun 25, 2014 at 11:51:51PM -, Maxim Kuvyrkov wrote: > How was "sleep" and system glibc compiled? > To get reliable stack traces GDB has to have access to either frame > pointer (-fno-omit-frame-pointer compiler flag) or to unwind tables > (-funwind-tables). In the absence o

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

How was "sleep" and system glibc compiled? To get reliable stack traces GDB has to have access to either frame pointer (-fno-omit-frame-pointer compiler flag) or to unwind tables (-funwind-tables). In the absence of either of these, GDB has to guess where stack frame boundaries are. In this case

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

Installing coreutils-dbgsym package 8.21-1ubuntu5 did not produce a more useful Stacktrace. Stacktrace: #0 0xb6e90fa6 in nanosleep () at ../sysdeps/unix/syscall-template.S:81 No locals. #1 0xa91e in ?? () No symbol table info available. Backtrace stopped: previous frame identical to thi

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

So my team is telling me this defect is blocking the usefulness of the long term test automation and crashes we're detecting there. Those tests are a key player in Ubuntu Engineering goals for RTM so I +1 the 'critical' status of this defect and will be checking it regularly for progress. -- You

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

you should be able to get these call stacks by using the dwarf debug info, which is usually found in the .ddbg packages. Are these packages installed when trying to run crash? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bug

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

Setting to critical because crashes from the phone fail to retrace. ** Changed in: gdb (Ubuntu) Importance: High => Critical ** Changed in: gdb (Ubuntu) Assignee: (unassigned) => Canonical Foundations Team (canonical-foundations) -- You received this bug notification because you are a

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

the frame unwinder on arm needs work. ** Also affects: gdb-linaro Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1325503 Title: gdb reports 'corrupt stac

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

** Description changed: - On armhf crash files fail to retrace and gdb reports 'corrupt stack' - errors + [Test Case] + sleep 120 & + kill -SEGV %1 + + Observe a corrupt stack in the generated crash file. + + Original Report + --- + On armhf crash files fail to retrace and gdb report

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

I built coreutils on utopic with DEB_BUILD_OPTIONS=nocheck,nostrip and did receive a good stacktrace from gdb. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1325503 Title: gdb reports 'corrupt stack

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

I installed the precise version of gdb (there was no gdb-minimal) on a utopic system and that also ended in a corrupt stack. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1325503 Title: gdb reports

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

I install the saucy version of gdb-minimal 7.6.1-0ubuntu3 on a utopic system and had the same corrupt stack. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1325503 Title: gdb reports 'corrupt stack'

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

I installed the trusty version of gdb 7.7-0ubuntu3.1 on a utopic system with the same results. A binary that had strip run against it results in a corrupt stack. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.ne

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

This is true with both gdb and gdb-minimal versions 7.7.1-0ubuntu3 in utopic. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1325503 Title: gdb reports 'corrupt stack' on armhf without symbols To ma

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

** Tags added: qa-touch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1325503 Title: gdb reports 'corrupt stack' on armhf without symbols To manage notifications about this bug go to: https://bugs.

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

** Changed in: gdb (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1325503 Title: gdb reports 'corrupt stack' on armhf without symbols To manage notification

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

Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gdb (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1325503 Title: gdb re

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

** Summary changed: - gdb reports 'corrupt stack' on armhf + gdb reports 'corrupt stack' on armhf without symbols -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1325503 Title: gdb reports 'corrupt s