This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
core dump build id
- From: Jeffrey Chen <cpthk at live dot com>
- To: "gdb at sourceware dot org" <gdb at sourceware dot org>
- Date: Tue, 25 Oct 2016 22:25:23 +0000
- Subject: core dump build id
- Authentication-results: sourceware.org; auth=none
- Authentication-results: sourceware.org; dkim=none (message not signed) header.d=none;sourceware.org; dmarc=none action=none header.from=live.com;
- References: <CY4PR13MB141401CB3B10969E11D4E5D5C7A80@CY4PR13MB1414.namprd13.prod.outlook.com>
- Spamdiagnosticmetadata: NSPM
- Spamdiagnosticoutput: 1:99
Hi gdb community:
I am looking into how to verify the local binaries version match with the binaries during the core dump generation. We found the way to do that is by adding build-id information into the binaries. The core dump generation will include all the build-id corresponding with all the binaries. We could verify the build-id by using the command `$ eu-unstrip -n --core core`. However, I noticed that when gdb loads the core dump and binaries, if we provide a wrong version of the binaries, it will not complain. gdb would still load them fine without any warning. Do you know if this is a bug, or is it purposely done this way? If so, what's the reason behind it? Thanks.
Ubuntu 16.04, kernel 4.4.0
gdb 7.11.1