From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24473 invoked by alias); 6 Dec 2016 02:37:05 -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 24394 invoked by uid 89); 6 Dec 2016 02:36:57 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.2 spammy=sysroot, H*r:sk:gdb@sou, mingw X-HELO: relay1.mentorg.com Received: from relay1.mentorg.com (HELO relay1.mentorg.com) (192.94.38.131) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Tue, 06 Dec 2016 02:36:55 +0000 Received: from svr-orw-mbx-03.mgc.mentorg.com ([147.34.90.203]) by relay1.mentorg.com with esmtp id 1cE5ck-00060Y-8p from Luis_Gustavo@mentor.com for gdb@sourceware.org; Mon, 05 Dec 2016 18:36:54 -0800 Received: from [172.30.7.171] (147.34.91.1) by svr-orw-mbx-03.mgc.mentorg.com (147.34.90.203) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Mon, 5 Dec 2016 18:36:51 -0800 To: "gdb@sourceware.org" From: Luis Machado Subject: mingw-w64's GDB 64-bit/32-bit debugging Reply-To: Luis Machado Message-ID: <6b0e1474-b965-ef37-bd0f-3b38aad07810@codesourcery.com> Date: Tue, 06 Dec 2016 02:37:00 -0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.5.1 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8"; format=flowed Content-Transfer-Encoding: 7bit X-ClientProxiedBy: svr-orw-mbx-01.mgc.mentorg.com (147.34.90.201) To svr-orw-mbx-03.mgc.mentorg.com (147.34.90.203) X-IsSubscribed: yes X-SW-Source: 2016-12/txt/msg00014.txt.bz2 Hi, The configure files don't tell much other than the difference between hosts (mingw/mingw64). Is a native mingw-w64 gdb capable of debugging 64-bit and 32-bit Windows processes or do we need a 32-bit gdb for a 32-bit process and a 64-bit gdb for a 64-bit process? Doing some tests i noticed ming-w64's 64-bit GDB doesn't quite like the 32-bit executable, choking on some 64-bit Windows symbol files and eventually getting an unexpected signal. --- [New Thread 9536.0x2358] Error while mapping shared library sections: `C:\Windows\SYSTEM32\ntdll.dll': not in executable format: File format not recognized Error while mapping shared library sections: `C:\Windows\system32\wow64.dll': not in executable format: File format not recognized Error while mapping shared library sections: `C:\Windows\system32\wow64win.dll': not in executable format: File format not recognized warning: Could not load shared library symbols for WOW64_IMAGE_SECTION. Do you need "set solib-search-path" or "set sysroot"? warning: Could not load shared library symbols for WOW64_IMAGE_SECTION. Do you need "set solib-search-path" or "set sysroot"? warning: Could not load shared library symbols for NOT_AN_IMAGE. Do you need "set solib-search-path" or "set sysroot"? warning: Could not load shared library symbols for NOT_AN_IMAGE. Do you need "set solib-search-path" or "set sysroot"? Error while mapping shared library sections: `C:\Windows\system32\wow64cpu.dll': not in executable format: File format not recognized [New Thread 9536.0x2740] gdb: unknown target exception 0x4000001f at 0x401633 Thread 1 received signal ?, Unknown signal. 0x0009e0d8 in ?? () (gdb) info shared From To Syms Read Shared Object Library No C:\Windows\SYSTEM32\ntdll.dll No C:\Windows\system32\wow64.dll No C:\Windows\system32\wow64win.dll No C:\Windows\system32\wow64cpu.dll 0x75080000 0x751546b4 Yes (*) C:\Windows\SysWOW64\kernel32.dll 0x74be1000 0x74d55bac Yes (*) C:\Windows\SysWOW64\KernelBase.dll 0x742f1000 0x743ad7d8 Yes (*) C:\Windows\SysWOW64\msvcrt.dll (*): Shared library is missing debugging information.