Many annoying warning messages in gdb

[Toby Huang]

Hello,

I am trying to debug my Chrome for ChromeOS binary in gdb. I remember back traces used to work beautifully about a few months ago. Then all of a sudden, I see many copies of this warning message cluttering my gdb output and making it difficult to debug:

warning: (Internal error: pc 0x55555ef79770 in read in CU, but not in symtab.)

I have the symbol_level = 2 in my out/Cros/args.gn. Why did gdb stop working as well as before?

Sincerely,

Toby

More details:

I'm using the following command line to run gdb:

gdb --args ~/chromium/src/out/Cros/chrome --user-data-dir=/tmp/chrome --login-manager

The back trace output looks like:

(gdb) bt                                                               [86/1977]
warning: (Internal error: pc 0x7ffff7e8d890 in read in CU, but not in symtab.)  <- what is up with all these warning messages?
warning: (Internal error: pc 0x7ffff7e8d8a7 in read in CU, but not in symtab.)  
warning: (Internal error: pc 0x7ffff7e8d8a7 in read in CU, but not in symtab.)  
warning: (Internal error: pc 0x7ffff7e8d887 in read in CU, but not in symtab.)  
warning: (Internal error: pc 0x7ffff7e8d887 in read in CU, but not in symtab.)  
warning: (Internal error: pc 0x7ffff7e8d870 in read in CU, but not in symtab.)  
warning: (Internal error: pc 0x7ffff7e8d887 in read in CU, but not in symtab.)  
warning: (Internal error: pc 0x7ffff7e8d8a7 in read in CU, but not in symtab.)  
warning: (Internal error: pc 0x7ffff7e8d8a7 in read in CU, but not in symtab.)  
#0  base::debug::(anonymous namespace)::DebugBreak() ()                        
    at ../../base/debug/debugger_posix.cc:317                                  
warning: (Internal error: pc 0x7ffff7e8d887 in read in CU, but not in symtab.)  
warning: (Internal error: pc 0x7ffff7e8d887 in read in CU, but not in symtab.)  
#1  0x00007ffff7e8d888 in base::debug::BreakDebugger() ()                      
    at ../../base/debug/debugger_posix.cc:340                                  
warning: (Internal error: pc 0x7ffff7e8d887 in read in CU, but not in symtab.)
warning: Could not find DWO CU obj/base/base/logging.dwo(0xfee6fc0aea01247f) [in
 DWP file libbase.so.dwp] referenced by CU at offset 0xa2c [in module /usr/local
/google/home/tobyhuang/chromium/src/out/Cros/libbase.so]
warning: (Internal error: pc 0x7ffff7c00101 in read in CU, but not in symtab.)
warning: (Internal error: pc 0x7ffff7bff940 in read in CU, but not in symtab.)
warning: (Internal error: pc 0x7ffff7c00101 in read in CU, but not in symtab.)

[Morten Stenshorne]

Toby Huang <toby...@chromium.org> writes:

> Hello,
>
> I am trying to debug my Chrome for ChromeOS binary in gdb. I remember
> back traces used to work beautifully about a few months ago. Then all
> of a sudden, I see many copies of this warning message cluttering my
> gdb output and making it difficult to debug:
>
> warning: (Internal error: pc 0x55555ef79770 in read in CU, but not in
> symtab.)

I had this problem too, but a "gn clean" and a rebuild made it go away.

--
Morten Stenshorne, Software developer,
Blink/Layout, Google, Oslo, Norway

[Toby Huang]

Awesome, that worked. Thanks Morten!