From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3775 invoked by alias); 6 Dec 2016 03:34:03 -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 3682 invoked by uid 89); 6 Dec 2016 03:33:55 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-4.6 required=5.0 tests=AWL,BAYES_00,RP_MATCHES_RCVD,SPF_PASS,URIBL_RED autolearn=ham version=3.3.2 spammy=wow64, WOW64, H*r:sk:cable.0, H*MI:sk:6b0e147 X-HELO: eggs.gnu.org Received: from eggs.gnu.org (HELO eggs.gnu.org) (208.118.235.92) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Tue, 06 Dec 2016 03:33:44 +0000 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cE6Ve-0000a9-F4 for gdb@sourceware.org; Mon, 05 Dec 2016 22:33:42 -0500 Received: from fencepost.gnu.org ([2001:4830:134:3::e]:55655) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cE6Ve-0000Zu-BQ; Mon, 05 Dec 2016 22:33:38 -0500 Received: from 84.94.185.246.cable.012.net.il ([84.94.185.246]:3953 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1cE6Vd-0003i5-NV; Mon, 05 Dec 2016 22:33:38 -0500 Date: Tue, 06 Dec 2016 03:34:00 -0000 Message-Id: <83bmwpk9y2.fsf@gnu.org> From: Eli Zaretskii To: Luis Machado CC: gdb@sourceware.org In-reply-to: <6b0e1474-b965-ef37-bd0f-3b38aad07810@codesourcery.com> (message from Luis Machado on Mon, 5 Dec 2016 20:36:50 -0600) Subject: Re: mingw-w64's GDB 64-bit/32-bit debugging Reply-to: Eli Zaretskii References: <6b0e1474-b965-ef37-bd0f-3b38aad07810@codesourcery.com> X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2001:4830:134:3::e X-IsSubscribed: yes X-SW-Source: 2016-12/txt/msg00015.txt.bz2 > From: Luis Machado > Date: Mon, 5 Dec 2016 20:36:50 -0600 > > 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? The latter, I'm afraid. > 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. Yes, GDB doesn't yet have code that implements the protocol for debugging WOW64 applications, and the unexpected and unhandled exception you see is a sign of that. I'm quite sure patches to that effect will be appreciated.