Re: How to disable GDB backtrace new behavior of including disassembly in backtrace ?

On 2019-12-24 7:30 a.m., William Tambe wrote:
> I do not have a python script loaded.
> What GDB command should I use to check whether I have a frame-filter ?

"info frame-filter"

You can also try to start gdb with `-nx`, which will inhibit it from reading
the various gdbinit files that could change the settings.  If that makes a
difference, it means that some gdbinit file (either in your home or system wide)
is responsible.

> 
>>
>> Are you able to reproduce this behavior with another program?  If so, could
>> you send a small reproducer (small source snippet to compile + GDB commands),
> 
> Yes, I am able to reproduce it with any program that I compile; here
> is a simple example where I can see the issue when breaking after
> calling printf() and using the command backtrace.
> ---
> #include <stdio.h>
> void myfunc() {
>         printf("Hello world!\n");
> }
> void main () {
>         myfunc();
> }

This is what I get:

Reading symbols from a.out...
(gdb) start
Temporary breakpoint 1 at 0x1150: file allo.c, line 6.
Starting program: /home/simark/build/binutils-gdb/gdb/a.out

Temporary breakpoint 1, main () at allo.c:6
6	        myfunc();
(gdb) s
myfunc () at allo.c:3
3	        printf("Hello world!\n");
(gdb) bt
#0  myfunc () at allo.c:3
#1  0x000055555555515a in main () at allo.c:6

Simon