This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Warning when using separate debug info file


> From: Tom Tromey <tom@tromey.com>
> Cc: LRN <lrn1986@gmail.com>,  gdb-patches@sourceware.org
> Date: Wed, 24 Apr 2019 13:28:47 -0600
> 
> Eli> But then why doesn't this happen on GNU/Linux?
> 
> Those platforms moved away from the .gnu_debuglink approach to use
> build-id instead.  See (info "(gdb) Separate Debug Files")

So you are saying that if you create a separate debug info file with
.gnu_debuglink on GNU/Linux, then GDB will display the same warning
when debugging the stripped binary?  I think someone said this didn't
happen on GNU/Linux.

> So I suppose this is just a bug but the cause remains unknown.

The place where this happens, addr_info_make_relative, maps addresses
to BFD addresses, and I wonder why .gnu_debuglink appears in the array
of sections the GDB looks up in the separate debug file.  Any ideas
why this happens?


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]