From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8070 invoked by alias); 9 Mar 2015 16:44:45 -0000 Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org Received: (qmail 8057 invoked by uid 89); 9 Mar 2015 16:44:44 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.4 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.2 X-HELO: out2-smtp.messagingengine.com Received: from out2-smtp.messagingengine.com (HELO out2-smtp.messagingengine.com) (66.111.4.26) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-GCM-SHA384 encrypted) ESMTPS; Mon, 09 Mar 2015 16:44:39 +0000 Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.nyi.internal (Postfix) with ESMTP id 7D3CE212AC for ; Mon, 9 Mar 2015 12:44:36 -0400 (EDT) Received: from frontend1 ([10.202.2.160]) by compute5.internal (MEProxy); Mon, 09 Mar 2015 12:44:38 -0400 Received: from [192.168.1.102] (unknown [31.51.206.246]) by mail.messagingengine.com (Postfix) with ESMTPA id 7443EC00295; Mon, 9 Mar 2015 12:44:37 -0400 (EDT) Message-ID: <54FDCDF0.6080602@dronecode.org.uk> Date: Mon, 09 Mar 2015 16:44:00 -0000 From: Jon TURNEY User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0 MIME-Version: 1.0 To: Benjamin Gilbert , gdb@sourceware.org Subject: Re: Trying to get GDB to find PE symbol file via build-id References: In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2015-03/txt/msg00009.txt.bz2 On 08/03/2015 22:52, Benjamin Gilbert wrote: > I'm trying to build a Win32 DLL with separate debug symbols, but I can't > seem to get GDB to automatically load a symbol file using the PE build-id > support added in ld 2.25. I'm running on Fedora 21 x86_64, with a gdb > built from binutils-gdb HEAD (3e95021) and configured with > "--target=i686-w64-mingw32". Sorry, this was not something that I needed, so I never got around to looking at what was needed to hook this up in gdb. At the moment, fetching the build-id for gdb is only implemented for ELF files (See gdb/build-ic.c:build_id_bfd_get()) It should be pretty straightforward to extend that to handle PE files as well, and add an interface to get the PE build-id out of BFD...