mirror of
https://github.com/espressif/binutils-gdb.git
synced 2025-05-17 15:26:36 +08:00

The problem appears when break in nested noreturn calls. panic_abort() and esp_system_abort() are noreturn functions: #0 0x4008779f in panic_abort () #1 0x40087a78 in esp_system_abort () Backtrace stopped: previous frame identical to this frame (corrupt stack?) Assembly listing: 40081ad4 <panic_abort>: 40081ad4: 004136 entry a1, 32 40081aeb: ffff06 j 40081aeb <panic_abort+0x17> ... 40085614 <esp_system_abort>: 40085614: 004136 entry a1, 32 40085619: fc4ba5 call8 40081ad4 <panic_abort> 4008561c <__ubsan_include>: 4008561c: 004136 entry a1, 32 PC register for frame esp_system_abort points to the next instruction after instruction with address 40085619. It is ENTRY instruction for __ubsan_include. This caused wrong unwinding because we are not in __ubsan_include at this frame. In general for noreturn functions there should be RET instruction. This is why it works in all other cases. PC register can point to entry instruction only for the innermost frame. It is not possible otherwise. The fix is making it not possible to go with not innermost frame into the code block which collects frame cache for frames when PC is on entry instruction.
…
…
…
…
…
…
…
…
…
…
…
…
README for GNU development tools This directory contains various GNU compilers, assemblers, linkers, debuggers, etc., plus their support routines, definitions, and documentation. If you are receiving this as part of a GDB release, see the file gdb/README. If with a binutils release, see binutils/README; if with a libg++ release, see libg++/README, etc. That'll give you info about this package -- supported targets, how to use it, how to report bugs, etc. It is now possible to automatically configure and build a variety of tools with one command. To build all of the tools contained herein, run the ``configure'' script here, e.g.: ./configure make To install them (by default in /usr/local/bin, /usr/local/lib, etc), then do: make install (If the configure script can't determine your type of computer, give it the name as an argument, for instance ``./configure sun4''. You can use the script ``config.sub'' to test whether a name is recognized; if it is, config.sub translates it to a triplet specifying CPU, vendor, and OS.) If you have more than one compiler on your system, it is often best to explicitly set CC in the environment before running configure, and to also set CC when running make. For example (assuming sh/bash/ksh): CC=gcc ./configure make A similar example using csh: setenv CC gcc ./configure make Much of the code and documentation enclosed is copyright by the Free Software Foundation, Inc. See the file COPYING or COPYING.LIB in the various directories, for a description of the GNU General Public License terms under which you can copy the files. REPORTING BUGS: Again, see gdb/README, binutils/README, etc., for info on where and how to report problems.
Description
Languages
C
51.8%
Makefile
22.4%
Assembly
12.3%
C++
6%
Roff
1.4%
Other
5.4%